Kustomize
Hard
Generation
An overlay's configMapGenerator uses the same name as one generated in the base, with no behavior set. What happens?
Select your answer:
Show answer and explanation
Answer: The build fails, because the default behavior, create, needs a new name
Explanation
create is the default and only makes new ConfigMaps. To change one generated in the base, the overlay sets behavior: merge to add or override keys, or behavior: replace to swap the whole contents.
More hard Kustomize questions
- 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?
- A replacement's target field doesn't exist yet in the target resource. What makes Kustomize add it?