Skip to content
SPECIFICTION
Get listed

Argo Rollouts

argoproj.github.io

Free plan WindowsmacOSLinuxSelf-hosted
Visit argoproj.github.io
Spec score 9.0 #1 of 29 in Progressive Delivery Software

What it is

Argo Rollouts is a self-hosted Kubernetes controller for managing how application updates reach users. It supports BlueGreen, Canary and Rolling Update strategies, with weighted traffic shifting through ingress controllers or service meshes. Without a traffic-routing provider, it can adjust ReplicaSet counts instead. Metric integrations let it assess KPIs and automate promotion or rollback, while leaving room for manual judgment. Supported providers include NGINX, AWS ALB, Istio and Traefik for traffic, and Prometheus, Datadog, New Relic, Graphite and InfluxDB for metrics. It can operate independently of Argo CD and respond to Kubernetes manifest changes whether they come from GitOps or traditional CI/CD. Each cluster running Rollout workloads needs its own controller and CRD; a Rollout specification covers one application, not dependencies among applications. Shared-resource or worker-queue applications may be a poor fit, and infrastructure applications are not recommended. Argo Rollouts is free and open source. It runs on Linux, macOS, Windows or self-hosted environments.

Spec sheet

Purpose
Argo Rollouts is a Kubernetes controller and set of CRDs for advanced deployment and progressive delivery.Read 2 Oct 2026 · argoproj.github.io
Integrations
Documented integrations include NGINX, AWS ALB, Apache APISIX, Istio, Linkerd, SMI, Prometheus, Datadog, New Relic, Graphite, and InfluxDB.Read 2 Oct 2026 · argoproj.github.io
Security
The project documents cosign verification of signed container images and SLSA Level 3 provenance for container image attestations.Read 2 Oct 2026 · argoproj.github.io
Argo CD
Argo Rollouts is a standalone project and does not require Argo CD, though the FAQ describes how the two can work together.Read 2 Oct 2026 · argoproj.github.io
Argo CD dependency
Argo Rollouts is standalone and does not require Argo CD or another Argo project.Read 1 Oct 2026 · argoproj.github.io
Artifact verification
Container images are cosign-signed and release artifacts have SLSA provenance that can be verified with cosign or slsa-verifier.Read 1 Oct 2026 · argoproj.github.io
Automated analysis
It can query metrics to assess KPIs and drive automated promotion or rollback during an update.Read 2 Oct 2026 · argoproj.github.io
Automation
Rollouts can perform automated promotions and rollbacks based on metric analysis, alongside manual judgement.Read 1 Oct 2026 · argoproj.github.io
CLI platforms
The installation docs provide kubectl plugin binaries for Linux and macOS, and the release artifact list also includes a Windows binary.Read 2 Oct 2026 · argoproj.github.io
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.Read 2 Oct 2026 · argoproj.github.io
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.Read 1 Oct 2026 · argoproj.github.io
Dashboard
An optional kubectl plugin provides command-line management and visualization, and the docs also list a dashboard installation manifest.Read 2 Oct 2026 · argoproj.github.io
Deployment strategies
It supports blue-green, canary, and rolling update strategies.Read 2 Oct 2026 · argoproj.github.io
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.Read 2 Oct 2026 · argoproj.github.io
High availability
The controller can run with multiple replicas for high availability by enabling leader election.Read 2 Oct 2026 · argoproj.github.io
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.Read 2 Oct 2026 · argoproj.github.io
Metrics
Metric provider integrations include Prometheus, Wavefront, Kayenta, Web, Kubernetes Jobs, Datadog, New Relic, Graphite, and InfluxDB.Read 1 Oct 2026 · argoproj.github.io
Notifications
The Notifications Engine supports configurable triggers and templates, including integrations such as Slack and Microsoft Teams.Read 1 Oct 2026 · argoproj.github.io
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.Read 1 Oct 2026 · argoproj.github.io
Release platforms
Release assets include CLI binaries for macOS, Linux, and Windows in amd64 and arm64 variants where provided.Read 1 Oct 2026 · argoproj.github.io
Scope limit
A Rollout specification focuses on a single application and does not manage dependencies among multiple applications.Read 2 Oct 2026 · argoproj.github.io
Traffic control
It can gradually shift traffic to a new version using ingress controllers or service meshes, and can also adjust ReplicaSet counts when no traffic routing provider is configured.Read 2 Oct 2026 · argoproj.github.io
Traffic management
It supports fine-grained weighted traffic shifting and integrations with ingress controllers and service meshes.Read 1 Oct 2026 · argoproj.github.io
Traffic providers
Supported traffic providers include AWS ALB, Ambassador Edge Stack, Apache APISIX, Google Cloud, Gateway API, Istio, Kong, NGINX, SMI, and Traefik.Read 1 Oct 2026 · argoproj.github.io
Vulnerability reporting
The security policy requests responsible disclosure by email and says security advisories are published through GitHub Security Advisories.Read 2 Oct 2026 · argoproj.github.io

Plans and prices

Free and open source Free Kubernetes controller and CRDs · self-hosted installation Read 2 Oct 2026 · argoproj.github.io

Every Argo Rollouts plan and price →

Strong points and limits

Strong points

  • Supports BlueGreen, Canary and Rolling Update strategies.
  • Automates promotions and rollbacks using metric analysis.
  • Works with traditional CI/CD or GitOps changes.
  • Free and open source; Argo CD is not required.

Limits

  • Each cluster needs its own controller and CRD.
  • Focuses on one application at a time.
  • Shared-resource and worker-queue applications may not work well.
  • Infrastructure applications are not recommended use cases.

Who it suits

It suits teams deploying Kubernetes applications that want progressive delivery, metric-based automation and optional manual approval. Teams should account for its per-cluster controller requirement and the stated limits around shared resources, worker queues and infrastructure applications.

Verdict

Argo Rollouts offers multiple update strategies, traffic controls and metric-driven automation for Kubernetes application releases. Its single-application scope and per-cluster controller requirement are important operational constraints.

Where Specifiction places it

Alternatives to Argo RolloutsAll alternatives →