Architecture · EKS · ArgoCD

Hub-spoke sync across three regions

A single ArgoCD instance in us-east-2 reconciles desired state for two spoke clusters in ap-south-1 and eu-west-1 — App-of-Apps pattern, ~150 workloads, ~40 microservices.

SYNC SYNC single pane of glass — sync state for ~150 workloads HUB 01 prod-master us-east-2 · 10.0.0.0/16 ArgoCD · App-of-Apps ~150 workloads · ~40 svcs SPOKE 02 prod-india ap-south-1 · 10.10.0.0/16 SPOKE 03 prod-eu eu-west-1 · 10.20.0.0/16 COMPUTE Karpenter spot + on-demand · all clusters SCALER KEDA ScaledObject → agent-orchestrator APM New Relic DaemonSet → single account EXT Zenduty paging · escalation policies LEGEND Hub / focal Spoke / cloud Platform addon ArgoCD sync Async / metrics

THE HEADLINE

One hub, two spokes, App-of-Apps

ArgoCD lives in prod-master. Both spoke clusters are registered as remote destinations; a single App-of-Apps tree fans out per-environment manifests on every sync.

Compute is uniform

  • Karpenter on all 3 clusters
  • Two NodePools: spot, on-demand
  • KEDA scales agent-orchestrator per cluster

Single pane for ops

One New Relic account receives APM + infra from every cluster. Alert conditions fan out to Zenduty for paging and escalation routing.

lab · eks · argocd trial 2 · diagram-design skill · full-editorial dark