DeployelmIntroductions to CI/CD and deployment platforms

GitOps and Kubernetes delivery

What is Argo Rollouts? An introduction to Argo Project's Kubernetes progressive delivery controller

By the Deployelm editorial team · Published · Updated

Argo Rollouts is a Kubernetes controller with a set of CRDs that provide advanced deployment strategies such as blue-green, canary, and progressive delivery. It addresses limitations of the native Kubernetes RollingUpdate strategy, including the lack of traffic control. It can also use metrics to promote or roll back a release automatically.

Tool
Argo Rollouts
Made by
Argo Project
Official site
argoproj.github.io/rollouts
Category
GitOps and Kubernetes delivery

Who makes Argo Rollouts

Argo Rollouts is developed by the Argo Project. The official website is linked below this page, and it is the place to check for current documentation and project details.

Official website: argoproj.github.io/rollouts

What Argo Rollouts is for

Argo Rollouts exists to give Kubernetes teams deployment strategies that the built-in RollingUpdate strategy does not offer. The native strategy has no traffic control, so a team cannot decide how much traffic a new version receives while it is being rolled out.

The native rolling update also cannot automatically abort and roll back. Argo Rollouts fills that gap by combining progressive delivery strategies with metric analysis, so a release can be promoted or rolled back based on measured results instead of manual judgment alone.

Who Argo Rollouts is for

The vendor states that Argo Rollouts is aimed at teams running large-scale, high-volume production Kubernetes environments. In those settings, an unchecked bad release affects a lot of traffic, which makes gradual exposure and automated reversal valuable.

Teams that already deploy to Kubernetes and need more control than a standard rolling update provides are the natural fit.

Notable capabilities

Argo Rollouts combines deployment strategies, traffic management, and metric analysis. Traffic control and metric providers are optional integrations that plug into the controller.

  • Blue-green update strategy, available as an alternative to the native rolling update.
  • Fine-grained, weighted traffic shifting, which controls how much traffic reaches a new version.
  • Automated promotions and rollbacks, so a release does not depend on someone watching it.
  • Customizable metric queries and analysis of business KPIs to inform promotion decisions.
  • Ingress controller integration with NGINX and ALB for gradual traffic shifting.
  • Service mesh integration with Istio, Linkerd, and SMI.
  • Metric provider integration with Prometheus, Wavefront, Kayenta, Web, and Kubernetes Jobs.

How Argo Rollouts fits GitOps and Kubernetes delivery

In the GitOps and Kubernetes delivery category, Argo Rollouts covers the release strategy itself: how a new version reaches users once a deployment has been triggered. It runs inside the cluster as a controller and extends Kubernetes through CRDs.

Within Deployelm's wider niche of CI/CD and deployment platforms, it sits at the deployment end of the pipeline. A CI system builds and tests an artifact, and a delivery mechanism applies it to the cluster. Argo Rollouts then governs how the change is exposed, using traffic shifting through an ingress controller or service mesh and metrics from a provider to decide whether to continue or reverse.

Frequently asked questions

What is Argo Rollouts used for?

Argo Rollouts is used to run advanced deployment strategies on Kubernetes, including blue-green, canary, and progressive delivery. It can shift traffic gradually and use metrics to drive automated promotion or rollback.

Who develops Argo Rollouts?

Argo Rollouts is developed by the Argo Project. Its official website is argoproj.github.io/rollouts.

Does Argo Rollouts replace the Kubernetes RollingUpdate strategy?

It addresses the limitations of the native RollingUpdate strategy, such as the lack of traffic control and the inability to automatically abort and roll back. It does so through a controller and CRDs that offer alternative strategies.

Which ingress controllers and service meshes does Argo Rollouts support?

It integrates with the NGINX and ALB ingress controllers and with the Istio, Linkerd, and SMI service meshes. These integrations are optional and are used to shift traffic gradually.

Which metric providers does Argo Rollouts work with?

It can query metrics from providers including Prometheus, Wavefront, Kayenta, Web, and Kubernetes Jobs. Those queries can drive automated promotion or rollback.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Deployelm is independent and is not affiliated with Argo Project. Product names belong to their owners. Features change; confirm details on the official website.