Kustomize
Hard
Concepts
What does the openapi field in a kustomization.yaml provide?
Select your answer:
Show answer and explanation
Answer: A schema with merge keys so strategic merge patches handle custom resources
Explanation
Kustomize ships OpenAPI data only for built-in Kubernetes types. The openapi field points at a schema with merge keys and patch strategies for your custom resources, so strategic merge patches can merge their lists instead of replacing them.
More hard Kustomize questions
- 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?
- Which field path selects the value of the env var SERVICE_HOST in the container named app, for a replacement target?