Scaling Argo CD
- Argo CD in a cluster scales horizontally and vertically
- A default install should handle 100s of app stacks fine (1000s of containers)
- Certain values can be changed based on different scaling needs. Needs like:
- Large number of clusters in a single Argo CD
- Large number of applications deployed in a single Argo CD
- Large number of commits on any App repo Argo CD is watching (esp. monorepos)
- Large number of repositories to poll/webhook in a single Argo CD
- Implementing Argo CD High-Availability (docs)
- Many questions answered by maintainers "Prod Best Practices" video
Argo CD architecture setup options
- Namespace scoped: One Argo CD per namespace
- In enterprise: Dev’s manage their own Argo CD in their namespace. HA not required
- Workload clusters: One Argo CD per cluster
- Most popular. Mgmt overhead grows with # of clusters. HA not required
- Control plane cluster: One Argo CD for multiple clusters
- Inevitable without tight IaC control. Reduces overhead, but SPOF . HA highly encouraged
- Hybrid: Argo of Argo’s. Central Argo CD deploys Argo CD to each cluster
- Akuity SaaS: Argo of Argo’s with more automation and easier management
