Topology-Aware Service Routing for Kubernetes is Coming Soon!
summary
A Kubernetes feature promises to route clients only to backends in the same zone to avoid cross‑zone charges, implemented as API additions plus kube‑proxy/DNS logic that filters a service’s IP list by topology. A prototype reduces returned endpoints (example: from five to three) by matching topologyKeys-based endpoint selection and uses node watches with a ~10‑minute heartbeat to track IP changes. Alpha exists but lacks some compatibility; plan is to move to beta with API changes and kube‑proxy integration. same-zone endpoint filtering
AI-written summary · about
chapters (7)
related talks
27mImproving Network Efficiency with Topology Aware Routing
27mInside Kubernetes Services
28mProxy Service: A New Network Traffic Abstraction in Kubernetes
34mSpreading Apps, Controlling Traffic & Optimising Costs in Kubernetes
22mSpreading Apps, Controlling Traffic & Managing Costs in Kubernetes
38mThe Untapped Power of Services - L7 Load Balancing Without a Service Mesh
18mLet There Be Topology-Awareness in Kube-Scheduler!
36mBack to basics, getting traffic into your Kubernetes cluster