When GitOps Becomes the Bottleneck: Scaling Argo CD for High-Churn Platforms
summary
Argo CD becomes the bottleneck when thousands of ephemeral environments trigger one commit and one Application per session; engineers replace per-session commits with durable templates and an automation layer that uses AppProject + ApplicationSet patterns to generate apps, reduces 40,000 commits to ~40 template files, and serves sessions from a pool of 500 namespaces with batching. Reconciliation tuning includes webhooks over polling and generate.path to avoid cache invalidation. Trade-offs: lost per-session Git history, larger blast radius for template bugs, and the need to shard control planes (hub‑and‑spoke or domain split).
AI-written summary · about
chapters (9)
- 0:00GitOps bottlenecks
- 3:09Hygiene platforms and Argo CD limits
- 8:17Breaking session-application coupling
- 14:13Namespace pooling strategies
- 17:27Optimizing Git for high-frequency changes
- 20:59Trade-offs of architecture
- 23:05Signs to split controllers
- 24:51End-to-end lab workflow
- 27:37Key takeaways
related talks
05mLessons from a Large-Scale GitOps Implementation
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
43mGitOps at Scale with and Argo CD on
10mKeynote Scaling GitOps Using ArgoCD Application Sets Lesson Learnt
13mHow GitOps Should I Be? Lessons from a Kinda-GitOps Environment
32mLessons learnt from implementing GitOps and Continuous Delivery at scale
37mPanel: Building a GitOps...
28mClick-Free Environment Promotion Driven by ApplicationSets Progre...