fluxcd/flagger

Health v2 · maintenance only

Adoption not part of the score

5395 stars · 803 forks observed · 2026-08-28

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

Flagger is a progressive delivery Kubernetes operator that automates canary releases, A/B testing, and Blue/Green deployments by gradually shifting traffic to new versions while analyzing metrics and running conformance tests. It is a CNCF graduated project in the Flux GitOps family and integrates with service meshes (Istio, Linkerd, Kuma, App Mesh) and ingress controllers (NGINX, Contour, Gloo, Traefik, Gateway API).

Use cases

• automate canary deployments on kubernetes
• zero downtime releases with traffic shifting
• a/b testing with session affinity for frontend apps
• blue/green deployments with traffic mirroring
• gitops-driven progressive delivery with flux
• automated rollback when metrics degrade
• canary analysis with prometheus metrics

When to choose

• you run services on Kubernetes and want automated, metrics-driven rollouts
• you use a service mesh or ingress controller and need gradual traffic shifting
• you practice GitOps with Flux and want declarative release automation
• you need automatic rollback on failed canary analysis or conformance tests

When to avoid

• your workloads are not on Kubernetes
• you have no metrics backend (Prometheus, Datadog, etc.) to drive analysis
• you need simple CI/CD pipelines without progressive delivery
• you deploy to VMs or bare metal outside a cluster

Facets

service · maturity stable

deployment monitoring alerting ci-cd feature-flags load-testing cloud-computing microservices monitoring cloud self-hosted go progressive-delivery canary-deployment gitops ab-testing blue-green-deployment service-mesh istio linkerd kubernetes-operator cncf traffic-shifting prometheus devops containers automation kubernetes docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="fluxcd/flagger")