Time to Migrate to Application Set
summary
Bank Hapoalim replaces hundreds of nearly identical Argo CD Application CRs with one ApplicationSet cluster generator manifest that renders per-cluster Helm values and overlays, migrates many repos into a mono repo, and automatically instantiates apps in multiple clusters using label selectors. Migration steps include identifying commonalities, choosing generators, and testing per-environment overlays; complex templates occur in ~20% of AppSets. Outcome: far fewer duplicated manifests and easier version lookup, with tradeoffs of large cluster secret labels and risk that one AppSet change impacts many clusters.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:53Argo CD and its role
- 3:02Managing multiple apps
- 3:22Argo CD Application Set
- 5:07How generators work
- 8:02Second speaker Alina
- 8:23Migration steps
- 9:49Example configs
- 13:00Monorepo benefits
- 14:06Maintenance advantages
- 14:27Limitations of Application Set
- 15:08Future considerations
- 16:15Conclusion
related talks
36mMulti-cluster, multi-apps, multi-value deployments using Argo CD Application Sets
35mManage More Clusters with Less Hassle, with Argo CD Application Sets
32mDeploy N applications to N clusters using Argo CD ApplicationSet
01h 38mScaling Multi-cluster Management with Argo CD and Application Sets
26mManaging GitOps Deployments in Multi-cluster Production Environments
27mDeclarative...ish? Fixing Hidden Argo CD Pitfalls in Your GitOps Setup
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale
34mInfrastructure at Scale Using ArgoCD