ArgoCD › Multi-cluster
What are the architectural models for multi-cluster ArgoCD (hub-spoke vs per-cluster)?
IntermediateAnswer
Hub-and-spoke runs one central ArgoCD (the hub) managing many remote clusters (spokes)—simple governance, single pane of glass, but the hub is critical and needs network/credentials to all clusters. The alternative runs an ArgoCD per cluster—more isolation and resilience, but more instances to operate. Choice depends on scale, security, and blast-radius tolerance.
Real-world example A company uses hub-and-spoke for central control, accepting that the hub cluster must reach every spoke's API.