Argo Rollouts
argoproj.github.io
- Free plan
- Windows
- macOS
- Linux
- Self-hosted
What Argo Rollouts is
Argo Rollouts is a Kubernetes controller and set of custom resource definitions for progressive delivery. It supports BlueGreen, Canary and Rolling Update strategies, including gradual weighted traffic shifts through supported ingress controllers and service meshes. Rollouts can query metrics to assess performance during an update and automate promotion or rollback, while also allowing manual judgment. Metric providers include Prometheus, Datadog, New Relic, Graphite and InfluxDB; traffic integrations include NGINX, AWS ALB, Apache APISIX, Istio, Kong and Traefik. Notifications can use configurable triggers and templates, including Slack and Microsoft Teams. Argo Rollouts is standalone and does not require Argo CD. It is free and open source, with self-hosted installation. Its operational scope is one application within one Kubernetes cluster: each cluster using Rollout workloads needs its own controller and CRD. A Rollout specification does not manage dependencies among multiple applications. Applications with shared resources or worker-style queue processing may not work well, and infrastructure applications are not recommended use cases.
Who it suits
Argo Rollouts is for teams managing progressive delivery for applications on Kubernetes. It may suit teams seeking automated metric-based promotion or rollback alongside manual decisions.
Good to know, and what to watch
- Supports BlueGreen, Canary and Rolling Update strategies.
- Can automate promotion and rollback based on metrics.
- Does not require Argo CD.
- Free and open source with self-hosted installation.
- Focuses on a single application in one cluster.
- Each cluster needs its own controller and CRD.
- Shared-resource or worker-style applications may not work well.
- Infrastructure applications are not recommended use cases.
Plans
Every plan and priceFree and open source
Open source
Getting started
- Visit https://argoproj.github.io/argo-rollouts/.
- Install the controller with standard or namespace-scoped manifests.
- Use the optional kubectl plugin for command-line management and visualization.
- Define a Rollout resource for the application in its Kubernetes cluster.
- Configure a supported traffic provider or use ReplicaSet count adjustment.
- Add metric analysis and promotion or rollback behavior as needed.
Limits to check
The free plan is a self-hosted Kubernetes controller and CRDs. Each cluster using Rollout workloads requires its own controller and CRD, and each Rollout specification is scoped to one application.
The verdict
Argo Rollouts gives Kubernetes teams traffic-shifting strategies and metric-driven rollout controls without requiring Argo CD. Its single-application, per-cluster scope and compatibility caveats make fit assessment important.
Questions people ask
How much does Argo Rollouts cost?
The listed Free and open source plan is free.
Does it require Argo CD?
No. Argo Rollouts is standalone, though it can work with Argo CD.
Which deployment strategies does it support?
BlueGreen, Canary, and Rolling Update strategies.
Can it automatically roll back an update?
Yes. It can analyze metrics and automate promotions or rollbacks, alongside manual judgment.
Where can it run?
It is self-hosted for Kubernetes. Listed platforms include Linux, macOS, Windows, and self-hosted deployment.
Does it support pipeline as code and approval gates?
Yes, both are listed as supported.
What the maker publishes
- Argo CD
- Argo Rollouts is a standalone project and does not require Argo CD, though the FAQ describes how the two can work together. source
- Argo CD dependency
- Argo Rollouts is standalone and does not require Argo CD or another Argo project. source
- Artifact verification
- Container images are cosign-signed and release artifacts have SLSA provenance that can be verified with cosign or slsa-verifier. source
- Automated analysis
- It can query metrics to assess KPIs and drive automated promotion or rollback during an update. source
- Automation
- Rollouts can perform automated promotions and rollbacks based on metric analysis, alongside manual judgement. source
- CLI platforms
- The installation docs provide kubectl plugin binaries for Linux and macOS, and the release artifact list also includes a Windows binary. source
- Cluster scope limit
- Each cluster using Rollout workloads needs its own Rollout CRD and controller; a central controller cannot manage Rollout resources in external clusters. source
- Compatibility limits
- Applications using shared resources or worker-style queue processing may not work well with Argo Rollouts, and infrastructure applications are not recommended use cases. source
- Dashboard
- An optional kubectl plugin provides command-line management and visualization, and the docs also list a dashboard installation manifest. source
- Deployment strategies
- Rollouts supports BlueGreen, Canary, and Rolling Update strategies. source
- Deployment strategies
- It supports blue-green, canary, and rolling update strategies. source
- GitOps and CI/CD
- It reacts to Kubernetes manifest changes regardless of how they were made and can be used with traditional CI/CD that does not follow GitOps. source
- High availability
- The controller can run with multiple replicas for high availability by enabling leader election. source
- Installation
- The controller can be installed with standard or namespace-scoped manifests, and the kubectl plugin is optional. source
- Installation
- The controller can be installed with standard cluster-level manifests or with a namespace-level installation that requires the CRDs to be installed separately. source
- Integrations
- Documented integrations include NGINX, AWS ALB, Apache APISIX, Istio, Linkerd, SMI, Prometheus, Datadog, New Relic, Graphite, and InfluxDB. source
- Metrics
- Metric provider integrations include Prometheus, Wavefront, Kayenta, Web, Kubernetes Jobs, Datadog, New Relic, Graphite, and InfluxDB. source
- Notifications
- The Notifications Engine supports configurable triggers and templates, including integrations such as Slack and Microsoft Teams. source
- Operational scope
- The project currently supports a single Kubernetes deployment or application within a single cluster and requires a controller in each cluster using Rollouts. source
- Purpose
- Argo Rollouts is a Kubernetes controller and set of CRDs providing blue-green, canary, canary analysis, experimentation, and progressive delivery capabilities. source
- Purpose
- Argo Rollouts is a Kubernetes controller and set of CRDs for advanced deployment and progressive delivery. source
- Release platforms
- Release assets include CLI binaries for macOS, Linux, and Windows in amd64 and arm64 variants where provided. source
- Scope limit
- A Rollout specification focuses on a single application and does not manage dependencies among multiple applications. source
- Security
- Security vulnerabilities can be reported confidentially to [email protected], with advisories published through GitHub Security Advisories. source
Checked against the maker's pages on 2 Oct 2026.