Gateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
summary
New Gateway API introduces Kubernetes resources that separate concerns into GatewayClass/Gateway/Route model so infra teams provision load‑balancer classes, cluster operators instantiate Gateways, and app teams control routing (HTTP/TCP/TLS) including header matching, traffic splitting (percentage or header‑based canaries like 10%), and multi‑cluster backends via ServiceExport/ServiceImport. Implementations already tested include Contour, Istio, Traefik, Kong and GKE; design adds core/extended/custom conformance levels, webhook validation and demoed working examples of portability and layered rollout without redeploying routes.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:46Agenda
- 1:26Ingress API
- 2:59Background
- 4:14Gateway Class
- 6:44Why Gateway API
- 9:40Key Concepts
- 11:52Goals
- 14:29Portability
- 16:14Routes
- 17:13Twoway handshake
- 18:19Ingress
- 19:32Contour
- 21:33Second Demo
- 23:31Third Demo
- 30:20Roadmap
- 30:51Next Steps
related talks
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
50mGateway API, a Decade of Maturation for a New Kubernetes API
50mGateway API, 10 Years of Maturation for a New Kubernetes API
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
36mGateway API The new way to travel north south
28mBeyond Kubernetes Ingress (with Gateway API)
01h 00mGateway API: Basics, Nuance, and the Real World
