GitOps repo layout for environment promotion
WHAT IT TESTS: multi-env GitOps design. OUTLINE: shared base plus per-env overlays via Kustomize or value files, promotion by PR moving a pinned version forward, separating app source from config repos. RED FLAG: branch-per-environment with merge drift.
WHAT IT TESTS: whether you can structure GitOps for safe, auditable promotion. ANSWER OUTLINE: use a base plus per-environment overlays (Kustomize bases/overlays or Helm with per-env value files), keep environment configs in directories not long-lived branches, and pin each environment to an explicit image or chart version. Promotion is a pull request that advances the pinned version in the next environment's overlay. Often split app source repos from a config repo. RED FLAG: branch-per-env causing merge drift and cherry-pick chaos.
Read the original → interview
- #gitops
- #kustomize
- #promotion
- #multi-environment
- #repository-structure
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.