Argo Rollouts 2026: Progressive Delivery as Standard in the GitOps Stack
Canary and blue-green releases, automated analysis, and v1.10.0: How Argo Rollouts makes releases on Kubernetes measurable and safe – and where it differs from Flagger.
Tag archive
Canary and blue-green releases, automated analysis, and v1.10.0: How Argo Rollouts makes releases on Kubernetes measurable and safe – and where it differs from Flagger.

A standard Kubernetes Deployment rolling update has no concept of "check whether this is actually...
Short answer: use a server-side flag check for an Express API, roll out by percentage, and let React...
A New Stack opinion argues that progressive rollouts are a solved problem while the validation step that actually gates them is still hand-built. From an on-call chair, that reframing is overdue.
Reduce deployment risk using canary releases, feature flags, and traffic shadowing. Learn how to dec

Launching new features shouldn’t feel like a gamble—but too often, it does. That’s where feature flag...

Let’s face it, software releases are no longer once-a-quarter events. Teams are deploying updates...

To understand about blue-green deployment with Argo Rollouts Continuous Integration (CI) and...