Keynote Scaling GitOps Using ArgoCD Application Sets Lesson Learnt
summary
ArgoCD is deployed with ApplicationSet generators to replace hundreds of hand-made Application CRDs and scale beyond the fragile app-of-app pattern; the team moves from unmaintainable single Application CRDs (fails at ~20–50 apps) to using ApplicationSet generators (SCM, Git, Matrix) to bootstrap clusters from a mono-repo, install observability/DNS, and deploy to dev/staging/prod. Production uses separate prod and non-prod orchestrators, workload identities for cross-cluster access, external ingress, Argo CD Vault plugin for secrets, and GitHub/GitLab webhooks to trigger syncs. SCM mono-repo provider and Argo CD Vault plugin are central.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:43Agenda
- 1:13The Problem
- 2:19Security
- 3:02POHAs
- 3:50Application Sets
- 4:35What are providers
- 5:10Provider generators
- 5:20Matrix generator
- 5:56Production Setup
- 6:23Bootstrapping
- 7:11ArgoCD Wall
- 7:42Secrets Management
- 8:02Webhook
- 8:27Cluster Setup
- 8:49Cluster Format
- 9:13Environment Names
- 9:37OIDC Integration
related talks
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
21mApplied GitOps with Argo CD Autopilot Using Multiple Clusters with an ApplicationSet
35mManage More Clusters with Less Hassle, with Argo CD Application Sets
36mMulti-cluster, multi-apps, multi-value deployments using Argo CD Application Sets
05mLessons from a Large-Scale GitOps Implementation
26mManaging GitOps Deployments in Multi-cluster Production Environments
43mGitOps at Scale with and Argo CD on
06mKeynote: Scaling Argo for the Enterprise