Lightning Talk: Managing the ‘Git’ Half of ‘GitOps’: How to Structure...
summary
Four concrete repo layouts are compared with pros and cons: application+config in one repo (easy to reproduce but risks CI loops and poor scaling), single repo with branch per environment (simple promotion but forces cherry‑picks), single repo with directories per environment (Argo/Flux recommended, copy/promotion operation, use GitHub CODEOWNERS for approvals), and one repo per environment (compatible with acquired teams). Recommends artifacts like Helm charts or Terraform modules to make promotions a single version change.
AI-written summary · about
related talks
09mLightning Talk: Best Practices on Organizing GitOps Repositories
35mGitOps Approaches and Trade-offs
30mOrganizing Teams for GitOps and Cloud Native Deployments
08mLightning Talk: Using Multiple Repos for an Argo CD Application? It’s Not as...
35mGitOps - the holy grail of devops
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
07mLightning Talk: Merging Best Practices with Reality: One Repository for Code and Helm