Streamlining API Governance: Kubernetes Native API Management
summary
Claims that the Kubernetes Gateway API (introduced in 2019) fixes Ingress limits by adding structured HTTPRoute resources, extensible backendRefs and custom resources and native filters for URL rewrite and header injection; demonstrates a concrete HTTPRoute that rewrites /orders to /orderlist, adds an x-order-id header, and routes POST traffic to the order service; shows WSO2 APK extending Gateway API for rate limiting and auth, and recommends Envoy as the cloud‑native data‑plane runtime.
AI-written summary · about
chapters (13)
- 0:00Introduction to API Governance
- 0:54Understanding Kubernetes Ingress
- 3:20Challenges with Kubernetes Ingress
- 6:34Introduction to Kubernetes Gateway API
- 7:51Features of Kubernetes Gateway API
- 10:29Comparing Ingress and Gateway API
- 13:47Extensibility and Custom Resources
- 15:22WSO2 APK and Advanced Features
- 16:58Evolution of API Gateways
- 18:33Envoy: The Preferred Solution
- 20:28API Management Architecture
- 22:55Standardization and Future of API Gateways
- 25:21Conclusion
related talks
24mLeveraging Gateway API for Kubernetes Native API Management
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
28mApplication delivery on k8s - the past, present and future
28mBeyond Kubernetes Ingress (with Gateway API)
26mGetting Hands-On with the New Kubernetes Gateway API
25mgRPC API Management With a Kubernetes Native API Management Platform
