DeployelmIntroductions to CI/CD and deployment platforms

GitOps and Kubernetes delivery

What is Flagger? An introduction to Flux Project's progressive delivery operator for Kubernetes

By the Deployelm editorial team · Published · Updated

Flagger is a progressive delivery operator for Kubernetes that supports canary, A/B testing, and blue/green deployments. It reduces release risk by shifting traffic gradually while measuring metrics such as success rate and latency. It automates analysis, testing, promotion, and rollback across these strategies.

Tool
Flagger
Made by
Flux Project
Official site
flagger.app
Category
GitOps and Kubernetes delivery

Who makes Flagger

Flagger is developed by the Flux Project. It is a CNCF project and part of the Flux family of GitOps tools. The official website is linked below this page.

Official website: flagger.app

What Flagger is for

Flagger is for releasing changes to production on Kubernetes with less risk. Instead of sending all traffic to a new version at once, it shifts traffic gradually and measures how the new version behaves, using indicators such as success rate and latency.

It automates the analysis, testing, promotion, and rollback steps for multiple deployment strategies. The decision to continue or reverse a release is therefore driven by measured results rather than by a person watching dashboards.

Who Flagger is for

The vendor describes Flagger as aimed at developers automating production releases. It suits teams that already run workloads on Kubernetes and want release verification built into the delivery process.

Teams that use Flux for GitOps can combine it with Flagger to build GitOps canary pipelines.

Notable capabilities

Flagger supports several release strategies and a range of traffic routers and metric sources. Its analysis step can be extended, and it can report progress to chat tools.

  • Canary deployments with progressive traffic shifting and session affinity.
  • A/B testing that routes traffic using HTTP headers and cookies.
  • Blue/Green deployments with traffic switching and mirroring.
  • Canary support for meshes and ingress such as Istio, Linkerd, Kuma, and Gateway API.
  • Traffic routing through an ingress controller or a service mesh compatible with Kubernetes Gateway API.
  • Analysis that can query metrics from Prometheus, Datadog, CloudWatch, New Relic, and others.
  • Custom metrics and webhooks that extend analysis, for example for acceptance or load tests.
  • Notifications to Slack, Microsoft Teams, Discord, and Rocket.

How Flagger fits GitOps and Kubernetes delivery

In the GitOps and Kubernetes delivery category, Flagger handles the progressive release step. As part of the Flux family of GitOps tools, it is designed to be combined with Flux, which lets a GitOps workflow include canary releases with automated analysis.

Within Deployelm's wider niche of CI/CD and deployment platforms, Flagger sits after build and test stages and after a change has been declared in a repository. It controls how that change is exposed to traffic, verifies it against metrics, and either promotes or rolls it back. It is licensed under Apache 2.0.

Frequently asked questions

What is Flagger used for?

Flagger is used to automate progressive delivery on Kubernetes. It shifts traffic gradually while measuring metrics such as success rate and latency, then promotes or rolls back the release.

Who develops Flagger?

Flagger is developed by the Flux Project. It is a CNCF project and part of the Flux family of GitOps tools.

Does Flagger support A/B testing and blue/green deployments?

Yes. Besides canary deployments, Flagger supports A/B testing, which routes traffic using HTTP headers and cookies, and Blue/Green deployments, which support traffic switching and mirroring.

Does Flagger work with Flux?

Yes. Flagger can be combined with Flux to build GitOps canary pipelines.

Which metric providers and notification channels does Flagger support?

Analysis can query metrics from Prometheus, Datadog, CloudWatch, New Relic, and others. Flagger can send notifications to Slack, Microsoft Teams, Discord, and Rocket.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Deployelm is independent and is not affiliated with Flux Project. Product names belong to their owners. Features change; confirm details on the official website.