Leveraging Service Meshes for A/B, Blue-Green, and Canary Deployments (aka "Progressi...
summary
Demonstrates the open‑source Flagger operator controlling canary, A/B, Blue‑Green and traffic mirroring across Istio, Linkerd and AWS App Mesh using Prometheus metrics and CRDs that link to the deployment name. Progression uses configurable step intervals and a 50% max weight default, with automatic progressive rollbacks on error and webhook hooks for load or chaos tests. Integrates with GitOps via Flux/Helm, real deployments report intervals from minutes up to a week and it updates Git on success.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:22Flagger - The Progressive Delivery Operator
- 1:19Flagger overview
- 2:02Deployment Strategies
- 2:41Blue/Green - Deployment Strategy
- 3:15A/B Testing - Deployment Strategy
- 4:16Canary - Deployment Strategy
- 6:10Traffic Mirroring - Deployment Strategy
- 8:12Flagger - Service mesh automation
- 10:54Flagger. Canary CRD
- 17:29Canary CRD - Analysis spec
- 22:01Flagger - Validation process
related talks
16mProgressive Delivery with Flagger
33mProgressive Delivery Techniques with Flagger
46mProgressive Deployments with Consul Service Mesh
20mProgressive Delivery with the Kubernetes Gateway API
51mProgressive Delivery in the Kubernetes era
36mProgressive Delivery in the Kubernetes era
34mSupercharge Your Microservices CI/CD with Service Mesh and Kubernetes
01h 04mThe Fine Art of Canary Deployments
