# A custom resource refers to a generated ConfigMap by name, but after the build it still uses the name without the hash suffix. Why?

Kustomize, Hard (Expert), Troubleshooting. https://k8wiz.com/uquiz/a-custom-resource-refers-to-a-generated-configmap-by-name-but-after-the-build-it-still-uses-the-name-without-the-hash-suffix-why

- A. Kustomize only updates name references in fields it knows about
- B. Generated ConfigMaps can't be referenced by custom resources
- C. The hash is only added when the build runs with --enable-helm
- D. kubectl adds the suffix at apply time, not Kustomize

**Answer:** Kustomize only updates name references in fields it knows about

**Explanation:** Kustomize updates references through a list of known fields, such as a Pod's volumes and envFrom. List the CRD under the crds field so Kustomize learns its references, or set disableNameSuffixHash on that generator.