Why should you care?

Capstone infra piece — multi-cluster K8s, discovery, DR, and enterprise cloud-native patterns.

See it live — copy this example

Use AWS/Azure/GCP free tier or local Docker/Kind. Sketches and YAML are meant to be typed and adapted.

# CloudVerse multi-cluster GitOps
# Fleet repo: clusters/eu-prod, clusters/us-prod
# Argo CD ApplicationSet — generator: cluster list
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: payments-fleet
spec:
  generators:
  - list:
      elements:
      - cluster: eu-prod
        url: https://eu-prod.api.k8s.cloudverse.internal
      - cluster: us-prod
        url: https://us-prod.api.k8s.cloudverse.internal
  template:
    metadata:
      name: 'payments-{{cluster}}'
    spec:
      project: cloudverse
      source:
        repoURL: https://github.com/cloudverse/gitops
        path: apps/payments/overlays/{{cluster}}
      destination:
        server: '{{url}}'
        namespace: payments

What happened?

• Fleet management treats clusters as cattle.
• Consistent baselines; regional overlays for data residency.

Practice next

1. Register two lab clusters in Argo CD.
2. Deploy ApplicationSet.
3. Verify sync both regions.
4. Add Istio multi-cluster trust.
5. Centralize policy via OPA/Gatekeeper.

Remember

Fleet GitOps. Regional overlays. Consistent platform add-ons.

CloudVerse K8s fleet

Payments must run in EU and US clusters.

Outcome: One ApplicationSet keeps both regions aligned.