What is GitOps with ArgoCD hub-spoke model?

One central ArgoCD manages multiple clusters from a Git repo—no per-cluster installs. **Why use server: "*" in ArgoCD AppProjects?** ArgoCD resolves cluster names to server URLs for permissions; name: "*" fails syncs.

Does ArgoCD hub-spoke work for EKS multi-region?

Yes, via VPC peering and private endpoints—keeps it secure and low-latency.

🏗️ DevOps & Infrastructure

GitOps Hub-Spoke: ArgoCD's Secret to Taming Multi-Cluster Hell

Forget scattering ArgoCD everywhere. One hub rules six clusters, slashing overhead while delivering ironclad Git-backed state. This flips multi-cluster DevOps on its head.

theAIcatchup Apr 10, 2026 4 min read

ArgoCD hub-spoke diagram managing six EKS clusters via VPC peering

⚡ Key Takeaways

Hub-spoke ArgoCD slashes multi-cluster ops overhead to one unified control plane. 𝕏
Self-healing and Git-native rollbacks make drift a non-issue. 𝕏
AppProjects with server: '*' enforce RBAC across fleets — critical gotcha. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#AWS EKS #ArgoCD #EKS #GitOps #Kubernetes #Multi-cluster Kubernetes #Multi-cluster management #devsecops #hub-spoke #hub-spoke model

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

Kiro CLI + ArgoCD MCP: Finally GitOps Without the YAML Hell

Headlamp's 2025 Push: Kubernetes UI Finally Gets Multi-Cluster Legs

Two-Tier Service Accounts Fix Kubernetes AI Agent Chaos

Environment Variables: The 50-Year-Old Mess Still Breaking Your Deploys

Stay in the loop