Declarative...ish? Fixing Hidden Argo CD Pitfalls in Your GitOps Setup
summary
Four reproducible anti‑patterns and their fixes: hardcoding Helm data inside Application CRs mixes developer Helm values with static operator manifests, breaks local Helm testing and CI image updates; creating applications dynamically via CLI or envsubst loses Git history and disaster recovery because apps are not stored in Git; the Helm sandwich duplicates templating and versioning—replace nested Helm with ApplicationSets; write ApplicationSets instead of hundreds of individual apps (e g 50 apps for 10 clusters collapses to one appset) and keep all configs in Git.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:32Common Argo CD pitfalls
- 1:58Hard-coding application data
- 7:09Dynamic application creation
- 12:29Avoiding the helm sandwich
- 16:42Scaling with application sets
- 18:42Summary and takeaways
- 20:01Q&A and closing
related talks
25mGit Sh*t Done, the GitOps Way
02h 38mStop using kubectl, and use Git instead! - Hands-on GitOps workshop using Argo CD and Helm
29mWhen GitOps Becomes the Bottleneck: Scaling Argo CD for High-Churn Platforms
28mGitOps with Argo CD and Helm: Managing Your Kubernetes Repository
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
37mZero to GitOps: Automating RAG Workloads with Backstage Templates
01h 31mBeyond Patterns and Principles
31mSelf Healing GitOps: Continuous, Secure GitOps Using Argo CD, Helm and OPA