# argoproj/argo-rollouts

Progressive Delivery for Kubernetes

Repository: https://github.com/argoproj/argo-rollouts
Canonical: https://ross.abutalabs.com/products/argo-rollouts
Homepage: https://argo-rollouts.readthedocs.io/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: gitops, canary, bluegreen, kubernetes, argoproj, deployments, experiments, argo-rollouts, progressive-delivery, hacktoberfest
Last push: 2026-08-26T00:48:36+00:00

## Health v2 (maintenance only)
Score: 93/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 81, longevity 100
- inputs: {"age_days": 2846, "days_push": 8, "days_rel": 47, "gap_med": 61.5, "n_releases_24m": 7}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 3561, forks 1198 (observed 2026-08-28T04:08:09.802103+00:00)

## What it is
Argo Rollouts is a Kubernetes controller and set of CRDs that provides advanced deployment strategies such as blue-green and canary releases with progressive delivery. It integrates with ingress controllers and service meshes for weighted traffic shifting and can analyze metrics from external providers to automatically promote or roll back updates.

## Use cases
- run canary deployments on kubernetes with gradual traffic shifting
- blue-green deployments with automated rollback on failure
- automatically promote or abort releases based on metric analysis
- control rollout speed and blast radius beyond kubernetes rolling updates
- integrate canary releases with istio or nginx ingress traffic splitting
- add manual approval gates to kubernetes deployments

## When to choose
- you need canary or blue-green release strategies on kubernetes with fine-grained traffic control
- you want automated analysis-driven promotion and rollback using metrics providers
- you use istio, linkerd, nginx, or ALB and want to leverage their traffic shaping for releases
- you practice gitops with the argo ecosystem

## When to avoid
- you run simple services where kubernetes native RollingUpdate is sufficient
- you are not deploying to kubernetes
- you have no ingress controller, service mesh, or metrics provider to drive traffic shifting and analysis

## Facets
- artifact type: infra-config
- maturity: active
- function: deployment, monitoring, workflow-automation, configuration-management
- domain: cloud-computing, microservices
- platform: cloud, go, self-hosted
- tags: progressive-delivery, canary-deployment, blue-green-deployment, gitops, kubernetes-controller, crd, traffic-shifting, automated-rollback, service-mesh, argo-project, devops, containers, kubernetes, docker

## Member repositories
- argoproj/argo-rollouts (main) score 93

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:09.802103+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:34:12.814564+00:00, confidence not recorded.
  - readme: https://github.com/argoproj/argo-rollouts (fetched 2026-08-28T04:08:09.802103+00:00, sha 67a97691d4fb)
- Data as of 2026-08-30T08:39:29.467469+00:00.