History

xichengliudui 8e7aa29ef1 add istio 1.7 install command		2020-09-02 01:30:53 -07:00
..
dev	Change builtin metrics to work with Istio >= 1.5	2020-06-17 10:13:29 +03:00
install	📝 add documentation about Skipper Ingress (#15 )	2020-08-18 17:02:53 +02:00
tutorials	add istio 1.7 install command	2020-09-02 01:30:53 -07:00
usage	Merge pull request #671 from stealthybox/per-config-tracker-disable	2020-08-19 10:48:09 +03:00
README.md	📝 add documentation about Skipper Ingress (#15 )	2020-08-18 17:02:53 +02:00
SUMMARY.md	Docs tidy up	2020-08-19 11:29:08 +03:00
faq.md	docs: How to retry a failed release	2020-03-10 16:30:20 +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, Skipper, 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

Getting started

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

After install Flagger, you can follow one of the tutorials:

Service mesh tutorials

Ingress controller tutorials

Hands-on GitOps workshops