A school district keeps shared Kubernetes manifests in git and needs lab versus production differences without duplicating every file. Which Kustomize pattern best separates common definitions from environment-specific changes?
Select an answer to reveal the explanation.
Short Explanation
Shared base is the school’s common lesson plan; overlays are the sticky notes for lab versus prod. Kustomize keeps one base and layers env-specific patches so you are not photocopying every manifest twice. Hand-regenerating YAML or stuffing Secrets into the base is the opposite of that hygiene.
Full Explanation
Kustomize organizes configuration as a reusable base and overlays that apply strategic patches, images, and name prefixes per environment. School-district style lab and production clusters can share the base while overlays encode replica counts, ingress hosts, or resource limits. This reduces duplication compared with maintaining fully separate manifest trees.