Gateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
summary
Gateway API claims to replace Ingress limitations with GatewayClass/Gateway/Route resources that map to real roles (platform admin vs service owner), support cross-namespace routing, header-based canaries and weighted traffic splitting, and plug into existing infra like GKE Gateway controller plus Cloud Load Balancer, Cloud Armor and Certificate Manager. Gateway API graduated to beta July 2022, GKE controller is GA for single-cluster (Dec 2022) with multi-cluster preview, and 22 prior Ingress implementations motivated the change.
AI-written summary · about
chapters (10)
- 0:00Introduction to Gateway API
- 1:14Limitations of Ingress
- 3:47Gateway API core concepts
- 6:16Roles and hierarchy
- 9:20Advanced routing use cases
- 13:17GKE Gateway controller
- 17:33Multi-cluster functionality
- 20:56Multi-cluster services
- 23:14Gateway security model
- 25:30Community and Q&A
related talks
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
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)
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
33mExiting Ingress With the Gateway API
10mLightning Talk: Make Way for the Gateway
