Kustomize
Hard
Concepts
Why can a component patch resources defined in the overlay that includes it, when a base can't?
Select your answer:
Show answer and explanation
Answer: A base builds alone; a component runs against whatever includes it
Explanation
A base is a self-contained build, so its patches can only touch its own resources. A component is merged into the kustomization that lists it, so it can patch objects from the base or the overlay. That's why components suit optional features shared by several overlays.
More hard Kustomize questions
- 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?
- A strategic merge patch adds one item to a list in a custom resource, but the build replaces the whole list. Why?
- A custom resource refers to a generated ConfigMap by name, but after the build it still uses the name without the hash suffix. Why?
- 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?