Exiting Ingress With the Gateway API
Talkat KubeCon + CloudNativeCon North America 2022 · on Thursday, 2022-10-27· at 17:25· 252 AB, Huntington Place: 1 Washington Blvd·
summary
Gateway API graduates to Beta with 15+ implementations and a CRD-based install for Kubernetes 1.16+, promising features missing from Ingress: native traffic splitting (demoed 90/10 and 50/50 weights), cross-namespace backends protected by a two‑way ReferenceGrant handshake, and a Gateway resource that maps to either an in‑cluster proxy or cloud LB (GKE auto-provisions ILB/XLB). A migration helper called ingress-to-gateway generates equivalent Gateway and HTTPRoute YAML.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:20Ingress vs Gateway API
- 1:49Conformance levels
- 4:07API parallels and syntax
- 7:02Gateway resource concepts
- 10:05Advanced traffic management
- 14:06Getting started
- 15:38Practical implementation demo
- 23:45Migration and tools
- 24:49Future roadmap and community
related talks
28mBeyond Kubernetes Ingress (with Gateway API)
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
10mLightning Talk: Make Way for the Gateway
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
28mApplication delivery on k8s - the past, present and future
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
01h 00mGateway API: Basics, Nuance, and the Real World
43mGateway API: Beta to GA