GitOps in Pratice
summary
Shows concrete Argo CD promotion patterns: Dev uses helm wildcard tracking or branch-tracking to auto-deploy every new commit/version; Stage uses git tag tracking or constrained helm version ranges to promote only tagged releases; Production uses kubectl apply pinning to a specific Git SHA or pinned Helm version so nothing moves without an explicit application update. Demo runs on a local kind cluster, changes a web app background color and messages (0.110 → 0.111), and the workflows successfully sync as described.
AI-written summary · about
chapters (6)
- 0:00Introduction to GitOps
- 1:10Git-based promotion strategies
- 4:44Helm chart promotion strategies
- 7:14Live demo walkthrough
- 14:35KKP 2.21 improvements
- 15:17Q&A and closing
related talks
30mGitOps Syllabus: Working Our Way Through the Lesson Plan
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
27mImplementing GitOps with ArgoCD: A Practical Guide
25mGit Sh*t Done, the GitOps Way
34mGitOps Patterns for managing cloud native applications
30mManage your kubernetes cluster in the GITOPS way !!
30mThe Objectives And The Principles Behind GitOps
20mMulti-Stage Deployment Pipelines the GitOps Way