Hundreds of Clusters Sitting in a Tree with Argo CD
summary
Adobe-scale environment runs ~230 clusters, 22 regions and ~18,000 nodes (1.8 PB memory) and builds ephemeral full-API clusters per pull request using Argo CD, vcluster and the Cluster API. A PR triggers an ArgoCD ApplicationSet PR generator, Cluster API (or vcluster provider) provisions a virtual cluster as pods (vcluster ~30s, cloud LB 45–90s), Argo Events + Workflows register the cluster into Argo CD and sync bootstraps (Prometheus, rollouts); merge triggers automated delete — the demo provisions and tears down successfully.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:03Traditional dev cluster problems
- 2:52v-cluster for virtual K8s
- 4:56Cluster API provisioning
- 6:41Argo CD for GitOps
- 8:06PR clusters solve issues
- 9:52PR workflow end-to-end
- 11:00Demo: PR cluster creation
- 17:19Code snippets and repo
- 20:10Argo Events and CD workflow
- 21:12PR merge cleanup
- 22:37Argo Event Source execution
- 25:26Developer experience benefits
- 26:09Resources and contact
- 27:02Q&A: v-cluster scoping
- 28:04Q&A: Idea origin
- 29:13Q&A: Microservices in v-clusters
- 30:58Q&A
related talks
36mHow Adobe Planned For Scale With Argo CD, Cluster API, And VCluster
34mInfrastructure at Scale Using ArgoCD
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
21mMulti Cluster Magics With Argo CD and Cluster Inventory
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale
36mHow the @#$! Do I Deploy That Many Apps to That Many Clusters? How Adobe Scaled on GitOps
33mScaling to Thousands of Data & CI/CD Pipelines Using Argo and Virtual...
35mManage More Clusters with Less Hassle, with Argo CD Application Sets