Gateway API: Beta to GA
summary
Gateway API graduates core pieces—GatewayClass, Gateway, and HTTPRoute—to Beta as a CRD-based official Kubernetes API with webhook validation, requiring installing CRDs (not bundled in kube) and a conformance test suite. It already has 70+ contributors and about 15 implementations, supports advanced HTTP matching, header rewrites, filters and policy attachment, and keeps cross-namespace references behind a reference-policy alpha. v0.5.0 ships soon and conformance proves portability across implementations.
AI-written summary · about
chapters (19)
- 0:00Start
- 2:40Timeline
- 4:58Routes
- 6:41Conformance Levels
- 7:28Regex
- 8:05What's Changed in the Past Year
- 11:58Reference Policy
- 13:37Policy Attachment
- 14:50Build Extensions to the Api
- 17:11Stable Channel
- 19:59Pros and Cons
- 20:41Web Hook Validation
- 22:52Simple Http Route
- 24:26Filters
- 25:05Cross Namespace
- 28:36Graduation Criteria
- 31:56Egress Use Cases
- 39:36Admin Network Policy Api
- 41:14Supporting the Gateway Api
related talks
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
50mGateway API, 10 Years of Maturation for a New Kubernetes API
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
50mGateway API, a Decade of Maturation for a New Kubernetes API
01h 00mGateway API: Basics, Nuance, and the Real World
36mGateway API The new way to travel north south
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
