What it does
Argo Rollouts is a Kubernetes controller and custom resource set for progressive delivery. It supports blue-green and canary strategies, can pause for human approval, and can analyze metrics to decide whether to promote or abort an update. It complements Kubernetes Deployments with more control over release progression; it is not a general CI runner or a hosted deployment service. Traffic shaping integrations are optional but important when replica ratios alone are too coarse.
Walk a canary through its stages
The official getting-started guide requires a Kubernetes cluster with the Rollouts controller installed and the kubectl plugin available. Its example applies a Rollout resource and a Kubernetes Service, then updates the container image with the plugin. A canary specification can send an initial share of traffic to the new version, pause for a decision, and continue through later stages.
For a first evaluation, use a non-production cluster and follow the example through deployment, image update, watch, promotion, and abort. The guide shows kubectl argo rollouts get rollout ... --watch for observing progress, promote to continue a paused rollout, and abort to return to the stable ReplicaSet. These are documented example commands, not commands run here.
Rollouts can query metrics and use analysis to drive automated promotion or rollback. The project also documents integrations with ingress controllers and service meshes for weighted traffic shifts. Those integrations require their own configuration; without one, the basic Service-based example approximates a traffic percentage using replica counts.
The repository uses Apache License 2.0. There is no hosted plan or public support price on the project pages reviewed, so this entry covers the open-source controller. It belongs alongside, but is distinct from, Argo CD and Argo Workflows.
Strengths
- Canary and blue-green strategies add staged release controls beyond a standard rolling update.
- Metric analysis can be used to gate promotions or trigger automated rollback.
- The controller is published under Apache License 2.0.
Watch out for
- Evaluation requires a Kubernetes cluster, the controller, and the kubectl plugin.
- Fine-grained traffic shifting needs an ingress controller or service mesh; replica-based weights are approximate.
Best for
- Staging Kubernetes releases with a canary or blue-green strategy
- Teams that want metric checks and explicit promotion or abort steps in deployment
Sources
- Argo Rollouts (Oct 25, 2026)
- Basic Usage: Argo Rollouts (Oct 25, 2026)
- argo-rollouts LICENSE (Oct 25, 2026)