One API To Rule Them All? What the Gateway API Means For Service Meshes
summary
Argues that Gateway API becomes a single, Kubernetes-native way to express north‑south and east‑west routing by adding HTTPRoute for meshes so meshes can share one control surface; the gamma initiative coordinates vendors and in three months lands a first mesh routing milestone with 15+ implementations and an experimental/stable conformance model. Next targets are policy attachment and authorization, rate‑limiting and circuit‑breaking patterns, using vendor extensions when core APIs lack required features.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:36The Beginning
- 2:52A Unified Standard
- 6:55Gateway API
- 16:53Where are we going?
- 21:14Get involved
related talks
30mA Comprehensive Guide to API Gateways, K8s Gateways, and Service Meshes
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
38mAPI Gateways & Service Mesh: What’s best for us
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
28mA Look at Istio's Journey with the Gateway API
36mGateway API The new way to travel north south
24mTransform Your Network: Master API Control & Security
24mLeveraging Gateway API for Kubernetes Native API Management