Argo Rollouts 1.10 lands with new canary features

Argo Rollouts, the Kubernetes tool that lets you ship new versions without nuking your old setup, just released a candidate for version 1.10. It’s built for teams running containers at scale — think microservices, blue-green deploys, and canary tests where you roll out to 10% of users first to make sure nothing breaks.

This release adds support for traffic splitting using the Istio service mesh, which means you can route a small slice of real user traffic to a new version and watch how it behaves before pushing it fully live. There’s also a new experimental feature for automated rollback when health checks fail, so you don’t have to babysit every deployment.

The tool runs inside your cluster. You define what a rollout looks like in YAML, and the controller handles the rest — pausing, checking metrics, rolling back if needed. It’s the kind of thing a mid-size dev shop uses to sleep better at night instead of waking up at 2am because a bad deploy crashed production.

The candidate build is already live for folks who want to test it before the stable release. No major breaking changes from 1.9, so if you’re already running 1.9, the upgrade path should be smooth.

Why this matters for us: Brown and Black dev shops often run lean teams with no on-call rotation, and tools like Argo Rollouts let us ship faster without needing a dedicated SRE team to watch every deploy.