We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug When defining global.extraEnv the helm templating add the extraEnv in the envFrom in the statefulset for the backend.
global.extraEnv
This is the bit of the template for the templates/backend/statefulset-backend.yaml
templates/backend/statefulset-backend.yaml
{{- with (concat .Values.global.extraEnv .Values.backend.extraEnv) | uniq }} env: {{- toYaml . | nindent 12 }} {{- end }} {{- with (concat .Values.global.extraEnv .Values.backend.extraEnvFrom) | uniq }} envFrom: {{- toYaml . | nindent 12 }} {{- end }}
The with statement is
with
{{- with (concat .Values.global.extraEnv .Values.backend.extraEnvFrom) | uniq }}
while it should be
{{- with (concat .Values.global.extraEnvFrom .Values.backend.extraEnvFrom) | uniq }}
To Reproduce Define global.extraEnv in the helm chart values.
Expected behavior Kubernetes fails to apply because the field envFrom has the wrong format.
envFrom
Environment: Kubernetes 1.32
Thanks a lot in advance and let me know if you want me to fix it.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
When defining
global.extraEnv
the helm templating add the extraEnv in the envFrom in the statefulset for the backend.This is the bit of the template for the
templates/backend/statefulset-backend.yaml
The
with
statement iswhile it should be
To Reproduce
Define
global.extraEnv
in the helm chart values.Expected behavior
Kubernetes fails to apply because the field
envFrom
has the wrong format.Environment:
Kubernetes 1.32
Thanks a lot in advance and let me know if you want me to fix it.
The text was updated successfully, but these errors were encountered: