Joe Julian

I'll label this as a bug, but I think it's not because it's not the linter that's throwing that warning. That error is coming from the values merge before it...

I was thinking about this some more... I wonder if you had json schemas for the values of the subcharts if it would fail the linter.

If I were doing it, I would just make the values match the files: ``` serverConfigFiles: bootstrap.properties: | http.port=9080 https.port=-1 circuitbreaker.allowHealthIndicatorToFail=false ... jvm.options: | -Xmx768m server.env: | test ``` Then...

If the configmap uses filenames in the data, then you only need to mount the configmap: ``` volumes: - name: {{ .Values.configs.volumeMountsVar.name }} configMap: name: {{ .Values.configs.configName }} ``` Each...

I've reviewed the automated close. The correct way to do this is to specify multiple values files when using the helm cli.

The way I do it is to have different values files: dev.yaml ``` fullName: myrelease-dev deployment: replicas: 1 ``` prod.yaml ``` fullName: myrelease-prod deployment: replicas: 10 ingress: enabled: true ```...

Sure, you could do it that way. I'd be wary of exceeding the storage limit of a secret for the release artifact. The release secret has to be able to...

Typically you would use [named templates](https://helm.sh/docs/chart_template_guide/named_templates/) for that, and template the name so you can include it for both the PV name, and any place you need to reference that...

I would prefer we not do this in this fashion, but instead do what kubectl does with `--dry-run=`. I think an interim change to just default to `--dry-run=client` if `--dry-run`...

Looking at kubectl help: ``` --dry-run='none': Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit...