Cyril Jouve
Cyril Jouve
hi, those lines broke helm commands using structured --output (json, yaml) and helm template (#11385). as a workaround, I guess you can redirect stderr to stdout (`2>&1`)
helm logs & interaction is a bit "confused" * users can't control granularity because there is a single --debug "all or nothing" * some modules use go "log" module, sometimes...
in #1710, work was done generate the store struct and dump it in the generated config. For this issue, the same struct must be reconciled in a k8s Secret (similar...
An alternative would be to put the content of the certs in the generated config without the indirection to a file (ca instead of ca_file, cert instead of cert_file, etc)
this can be tested [here](https://github.com/jouve/chart-testing/releases) with * https://github.com/helm/chart-testing/pull/601 * https://github.com/helm/chart-testing/pull/591 * https://github.com/helm/chart-testing/pull/510 * https://github.com/helm/chart-testing/pull/508
instead of a new flag, maybe apiVersion should be prepended instead of appended ?
another blocker for this PR ? I could help if needed :)
I create a CM with the cabundle ``` kubectl create cm cabundle --from-file=ca.crt=ca.crt ``` then I mount it in graphql pod: ```yaml portal: server: graphqlServer: volumes: - name: gitops-storage emptyDir:...