Reduce the risk of introducing a new software version in production by gradually shifting traffic to the new version while measuring metrics like HTTP/gRPC request success rate and latency.
Flexible Traffic Routing
Shift and route traffic between app versions using a service mesh like Istio, Linkerd, Kuma, OSM or AWS App Mesh. Or if a service mesh does not meet your needs, use an Ingress controller like Contour, Gloo, NGINX, Skipper or Traefik.
Besides the builtin metrics checks, you can extend your application analysis with custom metrics and webooks for running acceptance tests, load tests, or any other custom validation.
Flagger was designed to give developers confidence in automating production releases with progressive delivery techniques.
A benefit of using canary releases is the ability to do capacity testing of the new version in a production environment with a safe rollback strategy if issues are found. By slowly ramping up the load, you can monitor and capture metrics about how the new version impacts the production environment.
Flagger can run automated application analysis, testing, promotion and rollback for the following deployment strategies:
Canary (progressive traffic shifting)
A/B Testing (HTTP headers and cookies traffic routing)
Blue/Green (traffic switching and mirroring)
Flagger's application analysis can be extended with metric queries targeting Prometheus, Datadog, CloudWatch, New Relic, Graphite, Dynatrace, InfluxDB and Google Cloud Monitoring (Stackdriver).
Flagger can be configured to send notifications (opens new window) to Slack, Microsoft Teams, Discord and Rocket. It will post messages when a deployment has been initialised, when a new revision has been detected and if the canary analysis failed or succeeded.
You can build fully automated GitOps pipelines for canary deployments with Flagger and Flux (opens new window).
GitOps is a way to do Kubernetes cluster management and application delivery. It works by using Git as a single source of truth for declarative infrastructure and applications. With Git at the center of your delivery pipelines, developers can make pull requests to accelerate and simplify application deployments and operations tasks to Kubernetes.
- Progressive Delivery for Istio with Flagger and Flux (opens new window)
- Progressive Delivery for AWS App Mesh with Flagger and Flux (opens new window)
- Progressive Delivery for Linkerd and Contour with Flagger and Flux (opens new window)
If you have any questions about Flagger and progressive delivery:
- Read the Flagger docs (opens new window).
- Invite yourself to the CNCF community slack (opens new window) and join the #flagger (opens new window) channel.
- Check out the Flux talks section (opens new window) and to see a list of online talks, hands-on training and meetups.
- File an issue (opens new window).
Your feedback is always welcome!
Flagger is Apache 2.0 (opens new window) licensed and accepts contributions via GitHub pull requests.
Flagger was initially developed in 2018 at Weaveworks by Stefan Prodan. In 2020 Flagger became a Cloud Native Computing Foundation (opens new window) project, part of Flux (opens new window) family of GitOps tools.