Glow up Your Stateful Services with Progressive Delivery Using Argo Rollouts!
summary
Argo Rollouts runs blue/green and canary for stateful workers by combining Kubernetes downward API, Argo Rollouts ephemeral labels, and application auto-reload configuration so a new pod reads a preview queue or DB instead of production. Demo uses Go + RabbitMQ, mounts labels at /etc/podinfo, adds ~4 lines to watch and reload config, launches a preview queue, verifies isolation, then promotes and after ~19s the old pods stop and the new pods flip to production settings — the method works end-to-end.
AI-written summary · about
chapters (8)
- 0:00Introduction and overview
- 1:21Argo Rollouts basics
- 3:32Challenges with stateful services
- 6:28Key configuration components
- 7:54Architecting the solution
- 9:51The importance of developer collaboration
- 12:16Deployment demonstration
- 20:47Summary and Q&A
related talks
29mProgressive Delivery for Micro-Services Using Argo Rollouts and the Downward API
35mProgressive Delivery with Argo Rollouts
01h 27mProgressive Delivery with Argo Rollouts
30mProgressive Delivery Made Easy With Argo Rollouts
40mProgressive Delivery with Kubernetes and Argo Rollouts
25mJuggling Argo Rollouts for Progressive Delivery Across Multiple-Services
28mProgressive Delivery With Argo Rollouts and Kubernetes Gateway API for Multi-Directional...
24mArgo Rollouts from the Trenches – Next Level Progressive Delivery Best Practices