Skip to main content
Argo Rollouts is a Kubernetes controller for progressive delivery that gives you safer, more controlled application updates. It introduces a Rollout custom resource (CRD) that extends the standard Deployment to support advanced strategies such as Canary and Blue/Green updates, metric-driven analysis, traffic shaping, automated rollbacks, and optional manual approval gates. Argo Rollouts can gradually expose a new application version to a subset of users, query metric providers (for example, Prometheus) to validate health, and automatically revert to a previous stable revision if analysis fails. It also integrates tightly with GitOps tools such as ArgoCD for declarative, version-controlled delivery.
A flowchart titled "Argo Rollouts" that shows a canary deployment process: update to v2, incrementally increase canary weight (e.g., 5%), pause to collect and analyze metrics, then loop back on success or rollback on failure.
The diagram above shows a typical canary workflow:
  • Deploy a new revision (v2) alongside the stable revision.
  • Incrementally shift a percentage of traffic to the canary (for example, 5%).
  • Pause to collect and analyze metrics and probes.
  • If the analysis passes, increase the canary weight or promote to stable; if it fails, automatically rollback to the previous stable revision.
Argo Rollouts introduces the Rollout CRD (kind: Rollout). You continue to use ordinary Kubernetes primitives (Services, Ingress, etc.), but replace Deployments with a Rollout resource when you need progressive delivery features like canary or blue/green strategies and automated analysis.

​
Core features — what Argo Rollouts provides

  • Progressive delivery: Reduce blast radius by exposing changes gradually to a subset of users.
  • Rollout CRD: A first-class Kubernetes resource to manage advanced deployment workflows.
  • Canary releases: Route a small portion of traffic to a new revision, observe behavior, then increase exposure.
  • Blue/Green deployments: Run two parallel environments and switch traffic when the new environment is validated.
  • Analysis (metric providers): Query metrics from systems like Prometheus or Datadog to validate health gates during rollouts.
  • Traffic shaping: Control traffic fractions using ingress controllers or service meshes (for example, Istio) integrated with Argo Rollouts.
  • Automated rollbacks: Automatically revert to a known-good revision if probes or metric analysis fail.
  • GitOps integration: Works with ArgoCD for declarative, version-controlled rollouts.

​
Feature comparisons: when to use each strategy

FeatureUse caseExample
Canary ReleasesGradually validate a new version with a subset of users to limit impactRoute 5% -> 25% -> 100% traffic to v2 while analyzing latency and error rates
Blue/Green DeploymentsQuickly switch all traffic to a tested environment and roll back instantly if neededDeploy v2 to Green environment, run integration tests, switch Service selector to Green
Analysis (metric providers)Gate promotion based on real-time telemetryQuery Prometheus for increased error rate or latency changes during canary windows
Traffic ShapingFine-grained control of traffic distributionUse Istio VirtualService or ingress rules to direct precise weights to revisions
Automated RollbacksReduce manual response time to regressionsRevert to previous revision automatically when SLA thresholds are breached
GitOps IntegrationKeep rollouts declarative and auditableManage Rollout manifests with ArgoCD for versioned rollouts and easy audits
A presentation slide titled "Argo Rollouts Features" showing eight numbered items. The features listed are Progressive Delivery, Rollout CRD, Canary Releases, Blue‑Green Deployments, Analysis (metric providers), Traffic Shaping, Automated Rollbacks, and GitOps Integration.

​
How Argo Rollouts fits into your delivery pipeline

  • Observability-first deployments: Integrate metric providers (Prometheus, Datadog) and application probes to make promotion decisions data-driven.
  • Service mesh / ingress integration: Use Istio, Linkerd, or supported ingress controllers for traffic splitting and weight-based routing.
  • CI/CD and GitOps: Keep Rollout manifests in Git and let ArgoCD or your CI pipeline apply them to trigger controlled rollouts.
  • Safety and automation: Combine automated analysis and rollbacks with optional manual approval steps (pauses) to balance safety and speed.

​
Getting started resources

  • Read the Argo Rollouts documentation to understand CRD fields and examples.
  • Try a simple canary Rollout with a small traffic weight and a Prometheus-based analysis query.
  • Integrate with ArgoCD for GitOps-managed rollouts and audits.
This overview introduced the primary concepts and capabilities of Argo Rollouts. From here, explore example Rollout manifests, integrations with Prometheus and service meshes (for example, Istio), and how to configure automated analyses, pause steps, and manual approvals to make your Kubernetes deployments safer and more controlled.

Watch Video