Kustomize
Hard
Troubleshooting
A custom resource refers to a generated ConfigMap by name, but after the build it still uses the name without the hash suffix. Why?
Select your answer:
Show answer and explanation
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.
More hard Kustomize questions
- An overlay's configMapGenerator uses the same name as one generated in the base, with no behavior set. What happens?
- A kustomization sets namespace: team-a and includes a ClusterRole. What happens to the ClusterRole?
- In a strategic merge patch, what does $patch: replace inside a container's resources map do?
- A patch target sets name: app. Does it also match a Deployment named app-worker?
- A patch changes the metadata.name of its target, and the build fails. What allows the rename?
- Which query parameter of a remote resource URL sets how long Kustomize waits for the fetch?