Best Practices for GitOps Promotions
summary
Argo CD only syncs manifests to clusters; it is not a delivery pipeline. Best practices: model a product as a group of Argo CD applications across environments; prefer folders over branches for environment config so repo state is obvious; use immutable image digests not mutable tags and avoid promoting git hashes; expect ~80% of changes via images and ~20% via configuration; treat “production” as a target composed of multiple clusters/regions; consider Codefresh GitOps, Argo Image Updater or Octopus Deploy for promotion tooling.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:42Argo CD scope
- 2:08GitOps promotion tools
- 3:11Developer expectations
- 4:57GitOps promotions
- 5:18Applications versus products in GitOps
- 7:01Promoting changes
- 8:03Git hashes bad
- 10:30Semantic versioning
- 12:37Matching environments
- 13:41How developers perceive production environments
- 15:26Clusters vs environments
- 16:09Folders over branches
- 20:45Key concepts & best practices
- 22:07Hydration workflows
- 23:10Closing & resources
related talks
27mA Million Ways To Promote Changes Between Environments
27mImplementing GitOps with ArgoCD: A Practical Guide
04mA Holistic Approach to Software Delivery with Argo
59mPromotion Between Environme...
13mHow GitOps Should I Be? Lessons from a Kinda-GitOps Environment
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
32mGitOps and Multi-Environments: A Story of Promotion
34mGitOps Patterns for managing cloud native applications