Kustomize
Hard
Concepts
labels sets includeSelectors: false and includeTemplates: true. Where do the labels end up?
Select your answer:
Show answer and explanation
Answer: On the resources and their pod templates, but not on selectors
Explanation
includeTemplates adds the labels to spec.template.metadata, so Pods carry them for monitoring or cost tools, while includeSelectors: false keeps them out of selectors that Kubernetes won't let you change.
More hard Kustomize questions
- What does the openapi field in a kustomization.yaml provide?
- Two bases included by one overlay both define a ConfigMap named settings in the same namespace. What happens?
- 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?