# Why does generatorOptions.immutable: true work well with Kustomize's default hash suffix?

Kustomize, Hard (Expert), Generation. https://k8wiz.com/uquiz/why-does-generatoroptionsimmutable-true-work-well-with-kustomizes-default-hash-suffix

- A. The hash proves to the API server that nobody changed the data inside the cluster
- B. Immutable objects skip the hash, which keeps their names stable
- C. New data gets a new name, so the old immutable ConfigMap never has to change
- D. Kubernetes only accepts immutable ConfigMaps with hashed names

**Answer:** New data gets a new name, so the old immutable ConfigMap never has to change

**Explanation:** An immutable ConfigMap or Secret can't be edited, only deleted and recreated, and the kubelet stops watching it for changes, which lowers the load on the API server. With the hash suffix, every change already produces a new object. Without the hash, an apply that changes the data would fail.