Progressive Delivery with Flagger
summary
Flagger is a Kubernetes operator that automates canary releases plus A/B, traffic mirroring and blue‑green strategies by creating duplicate deployments (prefixed with -primary) and managing Istio, Linkerd, App Mesh, Contour, Gloo or NGINX routing. It evaluates releases with Prometheus metric templates or Datadog/CloudWatch queries, webhooks that run end‑to‑end or load tests, and a manual gating HTTP API. Integrations include Flux/ArgoCD/Jenkins X, alerting to Slack/Teams/Discord, and a roadmap for more metric providers and a conformance test operator.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:34What is Progressive Delivery?
- 1:45Flagger. Goals
- 3:12Flagger . Deployment Strategies
- 4:47Canary - Deployment Strategy
- 6:05Flagger - Release automation
- 8:03Flagger - Traffic management
- 8:51Flagger - Validation process
- 10:36Flagger - Metric Templates
- 11:12Flagger Alerting
- 11:46Flagger - Testing Webhooks
- 13:02Flagger. Manual Cating
- 14:55Flagger. Roadmap
- 15:35Hands-on Workshops
related talks
33mProgressive Delivery Techniques with Flagger
20mProgressive Delivery with the Kubernetes Gateway API
27mLeveraging Service Meshes for A/B, Blue-Green, and Canary Deployments (aka "Progressi...
25mProgressive Delivery with AWS App Mesh & Amazon EKS - Flagger
51mProgressive Delivery in the Kubernetes era
43mCloud-Native Progressive Delivery
15mLightning Talk: GitOps and Progressive Delivery with Flagger, Istio and Flux
46mKubernetes Native Continuous Deployment with FluxCD, Flagger, and Linkerd