eu-prod Environment: Minikube with its own ArgoCD # Architecture Decision: Isolated ArgoCD per Cluster # The Two Models # When you have multiple Kubernetes clusters, there are two ways to run ArgoCD:
Model A - Single ArgoCD, multiple cluster targets
eu-staging Environment: k3d with its own ArgoCD # What We Built # A staging environment on a k3d cluster, following the same isolated-ArgoCD pattern established in eu-prod-minikube. This completes the three-tier pipeline:
1 2 3 eu-dev-rancher → eu-staging-k3d → eu-prod-minikube (Rancher/k3s) (k3d) (Minikube) ArgoCD (dev) ArgoCD (staging) ArgoCD (prod) All environments run the same image versions: svc1:nginx:1.27, svc2:nginx:1.26. Promotion means bumping these tags in Git - ArgoCD on each cluster picks up the change.
eu-staging Environment: Minikube with its own ArgoCD # What We Built # A staging environment on a dedicated Minikube profile, following the same isolated-ArgoCD pattern as eu-prod-minikube. This completes the three-tier pipeline:
1 2 3 eu-dev-rancher → eu-staging-minikube → eu-prod-minikube (Rancher/k3s) (Minikube) (Minikube) ArgoCD (dev) ArgoCD (staging) ArgoCD (prod) All environments run the same image versions: svc1:nginx:1.27, svc2:nginx:1.26. Promotion means bumping these tags in Git - ArgoCD on each cluster picks up the change.
Minikube Profile Management # Quick reference for managing the Minikube profiles used in this repo (eu-prod, eu-staging) day-to-day.
Profiles in This Repo # Profile kubectl context Environment eu-prod eu-prod Production (Minikube) eu-staging eu-staging Staging (Minikube) List All Profiles # 1 minikube profile list Shows profile name, driver, state (Running / Stopped), Kubernetes version, and IP for each profile.