All 29 Multi-cluster questions
More in Multi-cluster
How do you target a subset of clusters (e.g., only production)? How do cluster labels help manage a fleet? What connectivity does the hub need to spoke clusters? How do you deploy region-specific configuration to clusters? How do you onboard a new cluster into an existing GitOps setup? How do you deploy different app versions to different clusters (e.g., staged rollout)? How do you view aggregated application status across clusters? Can you run ArgoCD per cluster instead of a central hub, and why? How do you deploy the same application to many clusters efficiently? How do you handle per-cluster configuration differences?
Advertisement
Back to results for “Applications”
ArgoCD › Multi-cluster

What is the difference between targeting a cluster by server URL vs name?

Intermediate

Answer

destination.server uses the exact API server URL; destination.name uses the human-friendly cluster name from its Secret. Names are more portable and readable (URLs can change), so referencing clusters by name is often preferred in templates and manifests.
destination:
  name: prod-eu   # portable; vs server: https://...
Real-world example Apps reference clusters by name so a changed API endpoint doesn't require editing every Application.

Common follow-ups: Why is name more portable than URL? | Where is the name defined?

Applications App of Apps Multi-cluster
All 29 Multi-cluster questions