Progressive Delivery with the Kubernetes Gateway API
summary
Flagger automates GitOps progressive delivery on Kubernetes by updating Gateway API canary weight fields to split traffic in increments (demo uses 10% steps every 15s up to a 50% promotion threshold) and evaluates Prometheus-backed metric templates like error rate <1% and latency <0.5s to decide rollback or continue. The demo shows a successful canary promoting v6.0.3 to primary. Recent additions include session affinity for sticky canaries and blue/green traffic mirroring for mirrored request comparison.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Service strategies
- 2:31Canary releases in detail
- 4:56Flagger introduction
- 6:24Kubernetes Gateway API
- 7:50Gateway API resources
- 9:37Flagger + Gateway API
- 10:18Demo: canary release
- 18:18New Flagger features
- 19:50Closing
related talks
16mProgressive Delivery with Flagger
33mProgressive Delivery Techniques with Flagger
36mProgressive Delivery in the Kubernetes era
51mProgressive Delivery in the Kubernetes era
41mProgressive Delivery in the Kubernetes era
35mLeveling Up Your CD: Unlocking Progressive Delivery on Kubernetes
23mTowards Better Canary Releases With Flagger and Gateway API
27mLeveraging Service Meshes for A/B, Blue-Green, and Canary Deployments (aka "Progressi...
