Lightning Talk: Best Practices on Organizing GitOps Repositories
summary
Recommendation is to stop using long-lived branches for environments and instead use a single-branch mono-repo with environment-per-folder, which avoids merges and cherry-pick complexity and supports arbitrary promotion order. Also split source and manifest repos (split repos for code and manifests). This pattern works with Kustomize, Helm (multiple values files), Argo CD and AppSets, and is used by Intuit and Adobe; a certification lab also demos Argo CD plus GitHub Actions copying files.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:51How to organize your GitHub repositories
- 1:44What not to do
- 2:43Longrunning branches
- 3:14Why GitOps
- 4:32Best Practices
- 6:02Folders
- 7:54Conclusion
related talks
08mLightning Talk: Managing the ‘Git’ Half of ‘GitOps’: How to Structure...
08mLightning Talk: Using Multiple Repos for an Argo CD Application? It’s Not as...
10mLightning Talk: Abstracting Away the Complexity of ArgoCD
30mOrganizing Teams for GitOps and Cloud Native Deployments
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
35mGitOps Approaches and Trade-offs
07mLightning Talk: Merging Best Practices with Reality: One Repository for Code and Helm
35mGitOps - the holy grail of devops