Gateway API: The Illustrated Guide to the Future of Kubernetes Networking
summary
Gateway API claims to replace messy Ingress annotations (some controllers had over 100 annotations) by enforcing an explicit GatewayClass–Gateway–Route hierarchy with clear role separation (infrastructure provider, cluster operator, app developer) and up to 64 listeners per gateway. Controllers act like compilers: they watch CRDs plus Secrets/ConfigMaps/EndpointSlices, resolve references, update status as the contract so kubectl apply success does not mean traffic works. Tools include an ingress-to-gateway migration and a controller-matching wizard; v1.6 lists gRPC, HTTP, TCP, TLS, UDP and backend TLS policy.
AI-written summary · about
chapters (12)
- 0:00Introduction to Gateway API
- 1:09Evolution from Ingress to Gateway API
- 4:00Gateway API ownership model
- 8:15Gateway class and gateway resources
- 10:45Route attachment and permissions
- 13:14Status and data plane validation
- 16:48Gateway API development process
- 19:44Feature support levels in Gateway API
- 21:30Controller as a compiler
- 24:44Reconciliation and dependency graph
- 25:49Migration and tooling support
- 27:13Q&A session
related talks
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
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
28mApplication delivery on k8s - the past, present and future
50mGateway API, a Decade of Maturation for a New Kubernetes API
50mGateway API, 10 Years of Maturation for a New Kubernetes API
28mBeyond Kubernetes Ingress (with Gateway API)