Juggling Argo Rollouts for Progressive Delivery Across Multiple-Services
summary
Argo Rollouts coordinates progressive delivery across interdependent services by staging paired rollouts (front end and back end), using a kustomize config map generator to emit unique, versioned configMaps so a rollout references its own config rather than mutating shared state, promoting with `rollouts promote` and driving the sequence from CI/CD. Works for blue/green or canary, and handles config-only changes. Caveat: when using Argo CD add pruneLast to avoid premature configMap deletion; use rollouts promote to switch traffic atomically.
AI-written summary · about
chapters (10)
- 0:00Progressive delivery with Argo Rollouts
- 3:36Blue Green vs Canary deployments
- 7:04Legacy apps scenarios
- 10:57Legacy version mismatch
- 13:45Synchronized rollouts solution
- 17:55Versioned configs with ConfigMaps
- 18:17Live demo: synchronized rollouts
- 23:18Automating deployment process
- 24:24ConfigMap generator warnings
- 25:06Summary & Q&A
related talks
35mProgressive Delivery with Argo Rollouts
29mProgressive Delivery for Micro-Services Using Argo Rollouts and the Downward API
30mProgressive Delivery Made Easy With Argo Rollouts
24mArgo Rollouts from the Trenches – Next Level Progressive Delivery Best Practices
26mGlow up Your Stateful Services with Progressive Delivery Using Argo Rollouts!
20mIntuitive Progressive Delivery Across Microservices in a Depe...
28mProgressive Delivery With Argo Rollouts and Kubernetes Gateway API for Multi-Directional...
40mProgressive Delivery with Kubernetes and Argo Rollouts