Gateway API The new way to travel north south
summary
SIG Network redesigns north‑south routing as the Gateway API, a CRD‑based official kube extension that supports L4 and L7 routing and enforces portability and extensibility. Core resources are GatewayClass Gateway HTTPRoute; features like URL rewrites and weighted traffic are first‑class fields, not controller annotations. Cross‑namespace access uses referenceGrant cross-namespace weight split. Implementations expose support levels and conformance tests; demos use Contour on GKE with an 80/20 canary and OpenTelemetry tracing to verify behavior.
AI-written summary · about
chapters (11)
- 0:00Gateway API intro
- 1:02North South traffic in K8s
- 3:31Ingress limitations for North South
- 9:56Gateway API as the solution to Ingress problems
- 11:44Gateway API resources and roles
- 14:15Demo setup overview
- 16:24HTTP routing with rewrites
- 19:13Weight-based traffic splitting
- 22:03Gateway API design decisions
- 27:30Gateway API recap and future
- 28:13Q&A on traffic splits
related talks
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
01h 00mGateway API: Basics, Nuance, and the Real World
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
43mGateway API: Beta to GA
28mBeyond Kubernetes Ingress (with Gateway API)
26mGetting Hands-On with the New Kubernetes Gateway API