Kustomize
Hard
Troubleshooting
Two bases included by one overlay both define a ConfigMap named settings in the same namespace. What happens?
Select your answer:
Show answer and explanation
Answer: The build fails, because two resources have the same ID
Explanation
Kustomize identifies resources by group, version, kind, namespace and name, and two with the same ID are a conflict. Give the bases different name prefixes, or move the ConfigMap into one shared base.
More hard Kustomize questions
- A JSON 6902 patch adds an annotation named example.com/owner. How is that key written in the patch path?
- Why can a kustomization build with the kustomize CLI but fail with kubectl apply -k?
- Why does generatorOptions.immutable: true work well with Kustomize's default hash suffix?
- Why can a component patch resources defined in the overlay that includes it, when a base can't?
- Which field path selects the value of the env var SERVICE_HOST in the container named app, for a replacement target?
- A production overlay lists a remote base with ?ref=main. What's the risk?