You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Render the .Values.extraEnvs list so we can use templated values in it.
Use case
This feature would solve the issue exposed in this example Values. When deploying "extra" resources, we cannot reference their name in extraEnvs by using the templated form.
extraDeploy:
- | apiVersion: v1 kind: Secret metadata: # templated name, for multi-env portability name: {{ include "common.secrets.name" (dict "defaultNameSuffix" "extra-env" "context" $) }} labels: {} # omitted type: Opaque data: CUSTOM_SECRET: {{ .Values.CUSTOM_SECRET | b64enc | quote }}# This would be set from command lineCUSTOM_SECRET: mySuperPasswordextraEnvs:
- name: CUSTOM_SECRETvalueFrom:
secretKeyRef:
name: how do we reference it without hardcoding the Release name here?key: CUSTOM_SECRET
This problem can be worked around by variabilizing the secret name, but then we must "not forget" to update it from an environment to another. Implementing this feature request would allow to write:
Proposed functionality
Render the
.Values.extraEnvs
list so we can use templated values in it.Use case
This feature would solve the issue exposed in this example Values. When deploying "extra" resources, we cannot reference their name in
extraEnvs
by using the templated form.This problem can be worked around by variabilizing the secret name, but then we must "not forget" to update it from an environment to another. Implementing this feature request would allow to write:
The text was updated successfully, but these errors were encountered: