In a Helm template for a pod, how do you add an array of environment variables from a values.yaml array named env?

• A. env: {{- range .Values.env }} - name: "{{ .name }}" value: "{{ .value }}" {{- end }}
• B. env: - name: PORT value: "8080"
• C. envFrom: - configMapRef: name: app-env
• D. env: {{- range .Values.env }} - name: "{{ .name }}" value: "{{ .value }}" {{- end }}

Answer: (A)

You render a list of environment variables by looping over the array you defined in values.yaml and emitting one env entry for each item. The pod spec expects env to be a YAML list of maps, where each map has a name and a value. By using a template range over .Values.env, you dynamically generate every env entry from the values you provide, so adding or removing variables in values.yaml automatically updates the rendered manifest.

In practice you write something like:

env:

{{- range .Values.env }}

• name: "{{ .name }}"

value: "{{ .value }}"

{{- end }}

With this structure, values.yaml should provide env as an array of objects, e.g.:

env:

• name: VAR1

value: "foo"

• name: VAR2

value: "bar"

This approach is ideal when you want to define multiple environment variables in a single place (values.yaml) and have the template expand them into the pod spec without hardcoding each one. Using envFrom to pull from a ConfigMap or other sources would populate variables differently and isn’t aligned with sourcing the variables from the values.yaml array itself.