Ross ROSS = Recommend OSS · open-source software intelligence for agents

argoproj/argo-rollouts resource

Progressive Delivery for Kubernetes observed · 2026-08-28

github.com/argoproj/argo-rollouts · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

93/100

  • Activity 99
  • Release rhythm 81
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 61.5
  • age_days: 2846
  • days_rel: 47
  • days_push: 8
  • n_releases_24m: 7

Full methodology

Adoption not part of the score

3561 stars · 1198 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

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

infra-config · maturity active

deployment monitoring workflow-automation configuration-management cloud-computing microservices cloud go self-hosted progressive-delivery canary-deployment blue-green-deployment gitops kubernetes-controller crd traffic-shifting automated-rollback service-mesh argo-project devops containers kubernetes docker

1 source

Member repositories

RepositoryRoleHealth v2
argoproj/argo-rolloutsmain93

For agents

markdown · JSON · MCP: product_card(name="argoproj/argo-rollouts")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem