back

Argo Rollouts canary with metric gates

5% → 25% → 50% → 100% progressive traffic, each step gated by Apdex / 5xx / business-KPI AnalysisRuns. Auto-rollback on threshold breach.

// 01 · GITOPS TRIGGER git push Helm chart bump ArgoCD sync to cluster Argo Rollouts controller drives the canary spec // 02 · PROGRESSIVE TRAFFIC SHIFT — EACH STEP GATED BY AN ANALYSISRUN 5% canary traffic pause 10 min AnalysisRun strict thresholds 25% canary traffic pause 10 min AnalysisRun 50% canary traffic pause 10 min AnalysisRun 100% promote to stable canary becomes stable New Relic queried · Apdex · 5xx rate · success rate · business KPIs // 03 · BREACH ON ANY GATE → AUTO-ROLLBACK, CANARY POD KILLED Auto-rollback e.g. Apdex drops by 0.05 at 5% → fleet reverts in seconds, 95% of traffic stayed safe // 04 · TRAFFIC PLANE — GLOO GATEWAY (HTTPROUTE WEIGHTS) Gloo Gateway · HTTPRoute weights set by Argo Rollouts plugin Stable pods · weight = 100 − canary% Canary pods · weight = canary% · upstream contrib for Gateway API + KEDA support
Argo Rollouts canary pipeline — each traffic step opens an AnalysisRun against New Relic. Apdex, 5xx or business-KPI breach → automatic rollback.

stanislas andujar · standujar.dev