Supercharge Your GitOps with ArgoCD Agent
summary
ArgoCD Agent replaces a single hub reconcilier with per-cluster agents so credentials stay local, reconcilers run inside each workload cluster, and the hub provides centralized observability. Two operational modes exist: managed mode (hub defines apps, low agent footprint, limited apps-of-apps) and autonomous mode (workload clusters are source of truth, no single point of failure, higher resource usage). It integrates with vanilla ArgoCD, needs PKI for agent–principal links, scales toward thousands of clusters, and a three-cluster demo shows autonomous syncing while a managed delete reveals a misconfiguration.
AI-written summary · about
chapters (17)
- 0:00Multicluster GitOps intro
- 2:20Why multicluster matters
- 5:49GitOps for modern apps
- 7:57ArgoCD as GitOps engine
- 9:01Managing multicluster with ArgoCD
- 10:04Challenges in multicluster ArgoCD
- 11:31Introducing ArgoCD Agent
- 12:37How Agent flips the model
- 14:28Agent architecture modes
- 18:48Managed vs autonomous modes
- 22:27Choosing between modes
- 27:00Key trade-offs
- 27:21Live demo setup
- 31:07Demo managed mode
- 32:48Demo autonomous mode
- 36:53Summary
- 38:18Q&A
related talks
23mScale GitOps With the Argo CD Agent and Open Cluster Management
27mImplementing GitOps with ArgoCD: A Practical Guide
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
42mLet's Learn About ArgoCD
17mRedefining the Multi-Cluster Story of Argo CD
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
29mDemystifying Gitops with ArgoCD
43mGitOps at Scale with and Argo CD on