A Kustomize configMapGenerator builds a ConfigMap from local files and appends a content hash to the name. Why does that hash suffix matter for Deployments that reference the generated ConfigMap?
Select an answer to reveal the explanation.
Short Explanation
The hash suffix is a burglar alarm on the config package: change the files, get a new name, and anything pointing at the old name must update—usually kicking a rollout so Pods actually see the new settings.
Full Explanation
configMapGenerator can produce names like my-config-<hash>. When generator content changes, the name changes; Deployments that reference the generated name via nameReference updates get a new Pod template and roll out. The hash does not convert types, clear etcd, or force zero replicas.