Ingress V2 and Multicluster Services
summary
Proposal defines a new resource model with GatewayClass and Gateway (proxy instance + capacity, TLS), a recursive VirtualHost for app routing, and heterogeneous backends; portability uses an expanding ring of portability (core, extended, custom) with per-feature conformance tests and requirement that extended features be statically checkable by admission. Multi‑cluster Services embed existing Ingress/Service YAML in a template and select clusters via a ClusterRegistry CRD; authors demo a controller wiring Kubernetes APIs to configure global HTTP(S) load balancing across clusters for low latency, canary, HA and hybrid use cases.
AI-written summary · about
chapters (12)
- 0:00Next "Ingress" API
- 2:22API models: Ingress (Beta)
- 4:37API models: IngressRoute
- 5:43What have we learned?
- 11:25VirtualHost extensibility
- 12:01Portability
- 15:22Future directions
- 16:00Multi-Cluster Services: Use Cases
- 17:23Multi-Cluster Services: User Journey 2
- 20:15Multi-Cluster Services: Workflow
- 21:26Multi-Cluster Services: FAQ
- 23:48Conclusion
related talks
31mHere Be Services: Beyond the Cluster Boundary with Multicluster Servi...
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
28mBeyond Kubernetes Ingress (with Gateway API)
33mExiting Ingress With the Gateway API
28mApplication delivery on k8s - the past, present and future
20mInside Kubernetes Ingress
49mAdvanced Ingress for Your Kubernetes Apps
34mMulticluster Ingress Powered by Kubernetes Cluster Registry - Greg Harmon & Nikhil Jindal