Argo Rollouts — Progressive Delivery for Kubernetes

What it is

Argo Rollouts is a Kubernetes controller that replaces the built-in Deployment resource with advanced deployment strategies. It supports canary releases with configurable traffic weight steps, blue-green deployments with instant traffic switching, and automated analysis-driven promotions that reduce the blast radius of bad releases.

The tool targets platform engineers and DevOps teams running Kubernetes in production who need safer deployment strategies than the default rolling update. It integrates with service meshes like Istio and Linkerd, plus ingress controllers like Nginx and ALB.

How it saves time or tokens

Without Argo Rollouts, teams either accept the risk of all-at-once deployments or build custom canary logic with shell scripts and manual traffic splitting. Argo Rollouts encodes these patterns declaratively in a CRD, eliminating hours of scripting per release pipeline. The AnalysisRun feature automatically queries Prometheus or Datadog metrics and promotes or rolls back without human intervention.

How to use

1. Install the Argo Rollouts controller and kubectl plugin:

kubectl create namespace argo-rollouts
kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/latest/download/install.yaml
brew install argoproj/tap/kubectl-argo-rollouts

1. Define a Rollout resource instead of a Deployment:

apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
  name: my-app
spec:
  replicas: 5
  strategy:
    canary:
      steps:
        - setWeight: 20
        - pause: {duration: 5m}
        - setWeight: 50
        - pause: {duration: 5m}
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
        - name: app
          image: my-app:v2

1. Watch the rollout progress:

kubectl argo rollouts get rollout my-app --watch

Example

apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
  name: api-server
spec:
  strategy:
    blueGreen:
      activeService: api-active
      previewService: api-preview
      autoPromotionEnabled: false
  selector:
    matchLabels:
      app: api-server
  template:
    metadata:
      labels:
        app: api-server
    spec:
      containers:
        - name: api
          image: api-server:v3

Related on TokRepo

• DevOps tools directory -- Other CI/CD and infrastructure automation tools
• Automation tools -- Broader automation solutions for development workflows

Common pitfalls

• Forgetting to install the CRDs before creating Rollout resources causes silent failures with no error feedback
• Canary traffic splitting requires a compatible ingress controller or service mesh; without one, Argo Rollouts falls back to replica-based splitting which is less precise
• Setting autoPromotionEnabled to true in blue-green mode bypasses the preview verification step, defeating the purpose of blue-green deployments