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
