A Hands-On Introduction to the Kubernetes Gateway API with Apache APISIX
summary
Demonstrates Apache APISIX as a Kubernetes Ingress controller converting YAML Ingress and Gateway API resources into routes, using etcd for config storage and showing basic path-based routing, header and query-parameter routing, and path stripping via APISIX annotations which creates vendor lock-in. Uses Gateway API resources to express the same routing natively and notes Gateway API reaches v1.0 while APISIX currently lacks the URL rewrite filter implementation so that demo rewrite does not work. Mentions 20+ Ingress implementations.
AI-written summary · about
chapters (7)
- 0:00Introduction to Gateway API
- 3:02Apache APISIX as Ingress Controller
- 8:58Demo with Ingress API
- 14:42Limitations of Ingress API
- 16:28Gateway API advantages
- 20:04Advanced Gateway API features
- 22:56Future of Gateway API
related talks
12mSimpler and more flexible Kubernetes Ingress: Apache APISIX
26mGetting Hands-On with the New Kubernetes Gateway API
28mBeyond Kubernetes Ingress (with Gateway API)
01h 00mGateway API: Basics, Nuance, and the Real World
50mGateway API, a Decade of Maturation for a New Kubernetes API
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
43mKubernetes Ingress and API Gateways
34mBack to Basics, Getting Traffic Into your Kubernetes Cluster
