How I Tricked ArgoCD Into Sharding on a Single Cluster
summary
ArgoCD sharding is cluster‑level only, so the fix is to make one cluster look like many by creating extra Kubernetes cluster secrets whose server URL differs only by a query parameter. The process uses ArgoCD secrets, a rollout restart, and a script/Terraform to retarget apps: in a demo with ~30 apps the config changes 15/15 and CPU shifts from a single hot pod to two balanced controllers (uploader reports 846m vs 6m before). Memory and cache costs increase so higher memory footprint per controller and fake clusters via secret URL query params are the main tradeoffs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:26Argo CD overview
- 3:31Problem with controller
- 8:02Bank cluster impact
- 10:31Argo CD sharding limits
- 13:44Fake sharding trick
- 20:15Live demo
- 26:00Assigning shards
- 28:37Moving apps to clusters
- 30:23Results and trade-offs
- 31:29Q&A
related talks
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale
34mInfrastructure at Scale Using ArgoCD
29mMastering Efficiency in Argo CD: Scaling Smarter, Not Costlier
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
21mSecure ArgoCD Multi-Cluster Management Across Clouds Without Static Tokens
01h 38mScaling Multi-cluster Management with Argo CD and Application Sets
17mRedefining the Multi-Cluster Story of Argo CD
21mMulti Cluster Magics With Argo CD and Cluster Inventory