OSS TanbouOn this page
Overview
Argo Rollouts is a Kubernetes controller plus Rollout CRD for progressive delivery. It adds blue-green and canary strategies, staged traffic changes, metric-driven analysis, manual promotion, and abort/rollback controls so teams can limit deployment blast radius.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Key features
Declare blue-green and canary delivery as a Rollout CRD
Rollout steps can pause, change weights, and require promotion, giving teams finer control than a standard RollingUpdate. Blue-green separates preview and active revisions, while canary delivery progressively changes exposure to a new ReplicaSet.
Connect traffic shaping and metrics to automated delivery decisions
The controller can integrate with ingress controllers and service meshes such as NGINX, ALB, and Istio, while Analysis can query metric providers such as Prometheus to drive automated promotion or rollback.
Sources: [1]
Observe rollout state and explicitly promote or abort changes
The official getting-started flow watches a Rollout, promotes a paused canary, and demonstrates aborting a bad update so the stable ReplicaSet is restored.
Sources: [2]
Best fit
Fits Kubernetes teams that need controlled production blast radius
It is particularly useful for high-traffic services and platform teams that want deployment progression to depend on staged exposure, operator judgment, or measurable service KPIs.
Sources: [1]
Before adoption
Operate the controller, CRDs, and any traffic or metric integrations as one delivery system
Argo Rollouts adds a controller and CRDs to the cluster. Advanced traffic shaping and automated analysis also depend on compatible ingress, service-mesh, and metric-provider configurations, permissions, and failure handling.
Sources: [1]
Basic canaries without a traffic router approximate weight through replica ratios
The basic getting-started example uses normal Kubernetes Service networking, so canary weight is approximated by the ratio of old and new Pods. Fine-grained traffic percentages require a supported routing integration.
Sources: [2]
Pin a stable version and review release and upgrade guidance
As of October 3, 2026, the latest stable release is v1.10.0. Production installs should pin an intended release and verify cluster and integration compatibility instead of relying on a moving latest URL.
Sources: [3]
Official sources
- [1]Argo Rollouts README(2026-10-03)
- [2]Argo Rollouts Getting Started(2026-10-03)
- [3]Argo Rollouts v1.10.0 release(2026-10-03)
- [4]Argo Rollouts Apache-2.0 license(2026-10-03)
Supplemental curator note
Argo Rollouts is useful when Kubernetes Deployments do not provide enough control over rollout speed, traffic, or automated verification. Advanced canaries should be designed together with the ingress, service-mesh, and metrics systems they depend on.
Try it in 3 steps
- 1
Install the Argo Rollouts v1.10.0 controller
Install the controller and CRDs into a test cluster. Pin the intended version and review upgrade and integration compatibility for production.
kubectl create namespace argo-rollouts && kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/download/v1.10.0/install.yaml - 2
Apply the official canary sample
Create the five-replica Rollout and Service used by the official guide to demonstrate weighted and paused canary progression.
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-rollouts/v1.10.0/docs/getting-started/basic/rollout.yaml && kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-rollouts/v1.10.0/docs/getting-started/basic/service.yaml - 3
Watch the Rollout resource
Observe the custom resource state. Use the official kubectl plugin flow when you want to continue with promotion and abort operations.
kubectl get rollouts.argoproj.io rollouts-demo -w
Growth
Growth trends · Last 30 days
3,592 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 36
- Open PRs
- 164
Development activity is still being collected.
Built with
Categories and tags
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- gitops
- canary
- bluegreen
- kubernetes
- argoproj
- deployments
- experiments
- argo-rollouts
- progressive-delivery
- hacktoberfest
- Stars
- 3,592
- Forks
- 1,219
- Watchers
- 38
- Open issues
- 498
- Contributors
- 394
- Owner type
- Organization
- Primary language
- Go
- License
- Apache-2.0
- Repository last updated
- Oct 2, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- containerd21,377 Stars
3 shared tag(s) · 2 shared category(s) · Same language
embed an industry-standard runtime daemon for image transfer, snapshots, container execution, and supervision beneath Kubernetes and container platforms
Go - Argo Workflows17,019 Stars
3 shared tag(s) · 2 shared category(s) · Same language
orchestrate container tasks on Kubernetes as DAGs or steps for batch, ML, data, and automation workflows
Go - Crossplane12,134 Stars
3 shared tag(s) · 2 shared category(s) · Same language
extend Kubernetes APIs to build cloud-native control planes for applications and infrastructure
Go - Istio38,428 Stars
3 shared tag(s) · 1 shared category(s) · Same language
add mTLS, traffic policy, and telemetry transparently between services
Go - Trivy38,205 Stars
3 shared tag(s) · 1 shared category(s) · Same language
Scan images, filesystems, repositories, VMs, and Kubernetes for CVEs, secrets, IaC issues, and licenses
Go - Digger / OpenTaco5,044 Stars
2 shared tag(s) · 3 shared category(s) · Same language
bring Terraform and OpenTofu review into existing CI
Go
Report incorrect information
Tell us if any listing information is incorrect or outdated.