Multi-Cluster Application Management
What you'll learn: How to use ArgoCD to manage and deploy applications across multiple Kubernetes clusters from a single control plane.
Why Multi-Cluster Management?
In production environments, you rarely operate just one Kubernetes cluster. You might have separate clusters for different environments (dev, staging, prod), geographic regions, or business units. Managing applications across all these clusters individually becomes a nightmare. ArgoCD solves this by letting you manage multiple clusters from one central ArgoCD instance.
Analogy: Think of it like a franchise headquarters managing multiple restaurant locations. Instead of visiting each location to update the menu, you send instructions from headquarters to all locations at once.
Registering Additional Clusters
Before ArgoCD can deploy to a cluster, you must register it. The ArgoCD instance running in your "hub" cluster needs credentials to access "spoke" clusters:
# List registered clusters
argocd cluster list
# Add a new cluster (uses current kubectl context)
argocd cluster add my-prod-cluster
This creates a service account in the target cluster and stores credentials in ArgoCD as a secret. The "in-cluster" entry represents the cluster where ArgoCD itself runs.
Multi-Cluster Application Patterns
Once clusters are registered, specify the target in your Application manifest:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: my-app-prod
spec:
destination:
server: https://prod-cluster-api-url
namespace: production
source:
repoURL: https://github.com/myorg/myapp
path: overlays/prod
The destination.server URL matches what argocd cluster list displays. You can now deploy identical or environment-specific configurations to different clusters from a single Git repository.
Key Takeaway: ArgoCD's multi-cluster management lets you register external Kubernetes clusters and deploy applications to them declaratively, centralizing GitOps operations across your entire infrastructure from one control plane.