Getting Hands-On with the New Kubernetes Gateway API
summary
Shows concrete migrations: an Apache APISIX ingress controller routes requests for two nginx services (left/right), URL rewrites work via vendor annotations with regex but break portability; controller CRDs add features but lock you to a vendor. The Gateway API provides native concepts (HTTPRoute, filters) and an experimental URL-rewrite filter, but the demo fails because the installed Gateway CRD version lacks that filter. Most implementations remain alpha/beta so recommendation is to prefer tested controller CRDs for production today.
AI-written summary · about
chapters (9)
- 0:00Kubernetes Gateway API intro
- 1:26Kubernetes networking evolution
- 3:56Hands-on Ingress API
- 9:25Ingress limitations and CRDs
- 12:49Why Gateway API
- 14:16Gateway API demo
- 16:46Experimental features
- 18:10Gateway API future
- 20:39Q&A
related talks
01h 00mGateway API: Basics, Nuance, and the Real World
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
28mBeyond Kubernetes Ingress (with Gateway API)
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
24mA Hands-On Introduction to the Kubernetes Gateway API with Apache APISIX
28mApplication delivery on k8s - the past, present and future
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs