Evolving the Kubernetes Ingress APIs to GA and Beyond
Talkat KubeCon + CloudNativeCon North America 2019 · on Thursday, 2019-11-21· at 15:20· Room 16AB - San Diego Convention Center, Mezzanine Level·
summary
Ingress moves into networking.k8s.io with concrete GA work: rename backend → defaultBackend, add pathType: Exact/Prefix/ImplementationSpecific (fixes ambiguous regex behavior), require Service backends but allow CRD backends via polymorphic resourceRef, and add hostname wildcard rules and ingressClass. Timeline targets migration from extensions (v1.14+) with GA work around v1.18. A separate evolution proposes Gateway/GatewayClass/GatewayRoute to split infra, operator, and developer roles, introduce bidirectional bindings for RBAC, conformance levels (core/extended/custom), and is currently a proposal seeking implementers.
AI-written summary · about
chapters (9)
- 0:00Ingress GA goals and updates
- 2:12Path and hostname improvements
- 6:32Ingress class and backends
- 8:12Timeline and deprecation
- 12:45Future API considerations
- 17:03Gateway API resource model
- 21:20API design challenges
- 24:38Portability and extensibility
- 27:43Q&A and conclusion
related talks
28mApplication delivery on k8s - the past, present and future
33mExiting Ingress With the Gateway API
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
28mBeyond Kubernetes Ingress (with Gateway API)
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
30mGateway to the Future: A Brief History of Kubernetes Ingress
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API