From Gatekeepers To Enablers: Empowering Developers With ApplicationSets
summary
Migrates 2,000+ Argo CD Applications across six regions and 11 environments to a centralized ApplicationSet platform, replacing a brittle app-of-apps monolith with ApplicationSet controllers and an app-of-apps-for-application-sets hierarchy. Uses SCM, Git and cluster generators plus the pull request generator for ephemeral previews; migration is deploy AppSet (it claims existing apps) then gradually remove legacy apps. Results: 200+ developers gain self-service ownership, sync times and failure rates drop, controller CPU/memory fall and reconcile latency approaches real time; use OAuth, labels and PR checks.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:06Argo CD scaling challenges
- 2:31App of apps pattern
- 4:15Limitations at scale
- 6:41Introducing ApplicationSets
- 8:07How ApplicationSets work
- 10:37Migration from app of apps
- 11:58Managing multiple ApplicationSets
- 13:22Tips for ApplicationSets
- 15:30Migration outcomes
- 16:33Key takeaways
- 17:36Q&A
related talks
10mKeynote Scaling GitOps Using ArgoCD Application Sets Lesson Learnt
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
21mApplied GitOps with Argo CD Autopilot Using Multiple Clusters with an ApplicationSet
36mMulti-cluster, multi-apps, multi-value deployments using Argo CD Application Sets
35mManage More Clusters with Less Hassle, with Argo CD Application Sets
28mClick-Free Environment Promotion Driven by ApplicationSets Progre...
32mDeploy N applications to N clusters using Argo CD ApplicationSet
29mWhen GitOps Becomes the Bottleneck: Scaling Argo CD for High-Churn Platforms
