Control Plane, Service, or Both? – Argo CD Multi-Cluster Architectures
summary
Compares two Argo CD deployment patterns and their trade-offs: a management cluster gives a single control plane but creates a single point of failure, requires scaling the API server, repo server and especially the application controller, and can incur large network egress costs; the per-cluster model distributes load and scopes credentials but duplicates SSO, RBAC and repo config and risks environment drift. Covers hybrid options, recommends app-of-apps patterns, and cites users running 10,000 application sets.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:18What is Argo CD
- 4:57Core Models
- 11:29Per Cluster Model
- 15:09Per Cluster Disadvantages
- 17:27Hybrid Models
- 18:06Instance Per Logical Group
- 19:56Instance Per Cluster
- 22:43Questions to Ask
- 25:04Final Thoughts
- 25:29Scalability Sig
- 26:51Free Course
- 27:14Questions
related talks
34mInfrastructure at Scale Using ArgoCD
17mRedefining the Multi-Cluster Story of Argo CD
33mLike Peas And Carrots: Argo CD And Crossplane For Infrastructure Management
01h 38mScaling Multi-cluster Management with Argo CD and Application Sets
29mMastering Efficiency in Argo CD: Scaling Smarter, Not Costlier
29mMulti-tenancy vs. Multi-cluster: When Shou...
21mApplied GitOps with Argo CD Autopilot Using Multiple Clusters with an ApplicationSet
36mMulti-cluster, multi-apps, multi-value deployments using Argo CD Application Sets