A Helm chart treats ConfigMaps as immutable and templates a new ConfigMap name when values change on upgrade. What side effect should the developer expect?
Select an answer to reveal the explanation.
Short Explanation
Immutable ConfigMaps are like sealed envelopes with a new barcode each rewrite—you do not erase the old seal; you issue a new envelope and point the app at it. Upgrades can leave old objects around until Pods reference the new name.
Full Explanation
Many charts use immutable ConfigMaps plus name hashing so content changes produce a new object and trigger a Deployment rollout when the Pod template references the new name. Expect additional resources and a need for Pods to mount or env-from the updated ConfigMap. Secrets are not mass-deleted, and registries are unrelated to ConfigMap hashing.