Flagger, Linkerd, And Gateway API: Oh My!
summary
Flagger automates progressive delivery by driving traffic shifts via Gateway API HTTPRoute objects rather than mesh-specific APIs; Linkerd ships an extension that watches HTTPRoute weights and translates them to Linkerd objects (service profile and destination) so canaries actually receive traffic. The demo shows Flagger moving 5% every 5s up to 95% using Prometheus metrics (success rate, latency) to decide roll forward or rollback, and the live demo works: HTTPRoute reflects the split and Linkerd enforces it. Linkerd service profile is used to apply routing.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:57Gateway API: Introduction
- 2:40Gateway API: How does it help?
- 3:43Progressive Delivery
- 7:48Flagger Overview
- 11:19How does Linkerd work?
- 12:16Gateway API: Networking Model
- 14:48Gateway API: Resources
related talks
40mDeep Dive: Linkerd
34mSupercharge Your Microservices CI/CD with Service Mesh and Kubernetes
37mIntro: Linkerd
38mRouting Your Microservices Architecture
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
27mService Mess to Service Mesh
29mThe rise of Layer 7, microservices, and the proxy war...
35mNavigating the Service Mesh Ecosystem
