flagger/docs/gitbook

description
Flagger is a progressive delivery Kubernetes operator

Introduction

Flagger is a progressive delivery tool that automates the release process for applications running on Kubernetes. It reduces the risk of introducing a new software version in production by gradually shifting traffic to the new version while measuring metrics and running conformance tests.

Flagger implements several deployment strategies (Canary releases, A/B testing, Blue/Green mirroring) using a service mesh (App Mesh, Istio, Linkerd, Kuma, Open Service Mesh) or an ingress controller (Contour, Gloo, NGINX, Skipper, Traefik, APISIX) for traffic routing. For release analysis, Flagger can query Prometheus, InfluxDB, Datadog, New Relic, CloudWatch, Stackdriver or Graphite and for alerting it uses Slack, MS Teams, Discord and Rocket.

Flagger can be configured with Kubernetes custom resources and is compatible with any CI/CD solutions made for Kubernetes. Since Flagger is declarative and reacts to Kubernetes events, it can be used in GitOps pipelines together with tools like Flux, JenkinsX, Carvel, Argo, etc.

Flagger is a Cloud Native Computing Foundation project and part of Flux family of GitOps tools.

Getting started

To get started with Flagger, choose one of the supported routing providers and install Flagger with Helm or Kustomize.

After installing Flagger, you can follow one of these tutorials to get started:

Service mesh tutorials

• Istio
• Linkerd
• AWS App Mesh
• AWS App Mesh: Canary Deployment Using Flagger
• Open Service Mesh
• Kuma

Ingress controller tutorials

• Contour
• Gloo
• NGINX Ingress
• Skipper Ingress
• Traefik
• Apache APISIX

Hands-on GitOps workshops

• Istio
• Linkerd
• AWS App Mesh

The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.