Application delivery on k8s - the past, present and future
summary
Chronicles the move from ClusterIP/NodePort/LoadBalancer and self‑managed L7 proxies (NGINX, Envoy) to Kubernetes Ingress controllers and now the Gateway API, claiming Gateways replace vendor annotations with native header and query routing via protocol‑specific CRDs (GatewayClass, Gateway, HTTPRoute) and a two‑way attach model that separates admin and developer concerns. Describes extensions like backendRef to non‑Kubernetes backends (S3), HTTPRoute filters, gRPC support in experimental form, and notes Ingress remains stable while Gateways add portability and finer RBAC.
AI-written summary · about
chapters (10)
- 0:00Application delivery intro
- 1:07Exposing apps with services
- 4:19NodePort and LoadBalancer limits
- 7:51Self-managed L7 proxy challenges
- 9:18Ingress simplified L7 routing
- 13:54Ingress limitations today
- 16:42Gateway API overview
- 22:44RBAC and multi-team access
- 25:12Gateway API extensibility
- 27:18Ingress vs Gateway API
related talks
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
30mGateway to the Future: A Brief History of Kubernetes Ingress
28mBeyond Kubernetes Ingress (with Gateway API)
24mLeveraging Gateway API for Kubernetes Native API Management
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
26mGetting Hands-On with the New Kubernetes Gateway API
50mGateway API, a Decade of Maturation for a New Kubernetes API
