Stage and production for the city grants portal should share one Helm chart but differ in image tag, replica count, and Service type. Where should those differences live?
Select an answer to reveal the explanation.
Short Explanation
Same recipe, different shopping list: values.yaml (or per-env values files) retarget image tag, replicas, and Service type without forking templates. Forking charts per environment is the anti-pattern for stage versus production.
Full Explanation
Helm expects environment differences—image tags, replica counts, Service types, ConfigMap keys—to come from values, not from duplicated templates. Stage and production stay one chart with different values files. Forking templates per environment creates drift. Dockerfile ENTRYPOINT and DNS zone files are not where chart retargeting belongs.