Gateway to the Future: A Brief History of Kubernetes Ingress
summary
Covers how Kubernetes routes external traffic from port‑forwarding and Service type=LoadBalancer to a single Ingress IP, shows demo wiring DNS with external-dns and a Kong-based Ingress (Kong Gateway / kongress) to serve multiple hosts from one IP, and uses Kong plugins to enforce rate limits: 5 / 10 / 100 reqs per minute by API key. Explains Ingress shortcomings (L7 only, annotation sprawl), the new Gateway API primitives (Gateway/GatewayClass/HTTPRoute, TCP/UDP, weighted routing) and notes the spec reaches v1.0 and Kong’s repo has 45,000 stars.
AI-written summary · about
chapters (6)
- 0:00Introduction and setup
- 2:20How Kubernetes networking works
- 7:57Limitations of Ingress objects
- 13:59Ingress controllers and plugins
- 21:52Future of Gateway API
- 26:52Q&A and closing
related talks
28mApplication delivery on k8s - the past, present and future
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
54mSupercharge your Kubernetes Ingress with Kong
43mKubernetes Ingress and API Gateways
28mBeyond Kubernetes Ingress (with Gateway API)
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
33mExiting Ingress With the Gateway API
27mProviding secure Ingress into a multi-tenanted cluster using GatewayAPI