Beyond Kubernetes Ingress (with Gateway API)
summary
Gateway API positions itself as the successor to Ingress and claims concrete gains: explicit resources like GatewayClass Gateway HTTPRoute, multi‑protocol routes (HTTP gRPC TCP UDP), and a conformance scheme of core/extended/custom plus conformance profiles with automated test reporting. A live demo uses a kind cluster with Kuma control plane and Envoy gateway to apply a Gateway and HTTPRoute exposing a demo web app backed by Redis the gateway gets an IP and the counter app is reachable in a browser. The ecosystem lists 20+ implementations and active GA work.
AI-written summary · about
chapters (11)
- 0:00Gateway API overview
- 1:39Ingress API limits
- 3:49What is Gateway API
- 7:20Gateway API resources
- 9:25Kong’s Gateway API journey
- 11:09Gateway API in Kuma
- 12:32Live demo: Gateway API with Kuma
- 16:29Beyond HTTP routes
- 18:16Roadmap to Gateway API General Availability
- 21:30Experimental features
- 24:21Get involved
related talks
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
33mExiting Ingress With the Gateway API
01h 00mGateway API: Basics, Nuance, and the Real World
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
28mApplication delivery on k8s - the past, present and future
10mLightning Talk: Make Way for the Gateway
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
