Taming the Traffic: Select...
summary
Nearly 30 Gateway API implementations exist and the panel gives a practical decision path: start with a feature-parity spreadsheet (use the conformance report and ingress table), narrow by data-plane differentiators (Envoy metrics, Hubble, static-asset strength, cloud integrations), then run three proof-of-concept clusters to measure CRD/version handling, observability, performance and migration cost. Expect experimental features like TCP/UDP routes, policy-attachment and inference extensions, plus tooling such as ingress-to-gateway and Endgate to ease migration.
AI-written summary · about
chapters (13)
- 0:00Gateway API panel intro
- 1:06Panelist backgrounds
- 2:51Switching from Ingress to Gateway API
- 7:05Choosing Gateway API implementation
- 9:17Gateway API for east-west and north-south traffic
- 10:22Day-two operations and debugging
- 13:33Standardization versus flexibility
- 16:51Implementation collaboration
- 19:44Upcoming Gateway API features
- 21:35Lightning round: Pain points and favorites
- 24:422025 roadmaps
- 25:31Open mic and audience questions
- 28:09Closing remarks
related talks
31mBehind the Scenes of Building a Gateway API Dataplane...
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
36mGateway API The new way to travel north south
01h 00mGateway API: Basics, Nuance, and the Real World
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
33mExiting Ingress With the Gateway API
28mBeyond Kubernetes Ingress (with Gateway API)
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API