Lightning Talk: The $10,000 Argo CD Mistake: Eliminating Phantom Sync...
summary
When Argo CD scales beyond 500 applications the repo server becomes the performance bottleneck, constantly polling Git and regenerating manifests — phantom syncs — which drives CPU and memory high. The fixes are concrete: increase polling intervals (default ~180s), switch to event‑driven webhooks with PR/tag filters, replace hundreds of manifests with ApplicationSet templates, and avoid full repo clones by optimizing git fetch. The result is lower CPU/memory (CPU <75%), 10x faster syncs, and roughly $10k of avoided cost.
AI-written summary · about
related talks
29mWhen GitOps Becomes the Bottleneck: Scaling Argo CD for High-Churn Platforms
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale
15mA Quantitative Study on Argo Scalability
29mMastering Efficiency in Argo CD: Scaling Smarter, Not Costlier
25mSailing Across the Ocean of Argo Ecosystem Like a Pro
10mKeynote: Pushing the Limits: Scaling ArgoCD’s Repo-Server To Handle 30...
43mGitOps at Scale with and Argo CD on
21mKey Takeaways from Scaling Adobe's CI/CD Solution to Support..