History

stefanprodan 3b8c285870 Move examples to tutorials docs		2020-02-18 18:13:20 +02:00
..
install	Update docs to Helm v3	2020-02-13 12:59:13 +02:00
tutorials	Move examples to tutorials docs	2020-02-18 18:13:20 +02:00
usage	Move examples to tutorials docs	2020-02-18 18:13:20 +02:00
README.md	Add Contour reference to docs	2019-12-20 11:47:00 +02:00
SUMMARY.md	Move examples to tutorials docs	2020-02-18 18:13:20 +02:00
dev-guide.md	Add development guide to docs	2020-02-18 18:12:23 +02:00
faq.md	Use header operations in Istio router	2020-02-14 13:59:36 +02:00
how-it-works.md	Release v0.23.0	2020-02-06 14:49:04 +02:00

README.md

description
Flagger is a progressive delivery Kubernetes operator

Introduction

Flagger is a Kubernetes operator that automates the promotion of canary deployments using Istio, Linkerd, App Mesh, NGINX, Contour or Gloo routing for traffic shifting and Prometheus metrics for canary analysis. The canary analysis can be extended with webhooks for running system integration/acceptance tests, load tests, or any other custom validation.

Flagger implements a control loop that gradually shifts traffic to the canary while measuring key performance indicators like HTTP requests success rate, requests average duration and pods health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack or MS Teams.

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 Flux CD or JenkinsX.

This project is sponsored by Weaveworks