Topology-Aware Service Routing for Kubernetes is Coming Soon!
summary
Kubernetes adds a feature that returns only same-zone endpoints so services avoid charged cross-zone traffic, implemented as an API + controller that watches nodes and filters service IP lists by topology domain. Kube-proxy/DNS return is limited to matching backends (alpha shows only label-based matching, not arbitrary attributes). Prototype uses node heartbeats (~10 minute update) and IP-list projection; current alpha has compatibility gaps and known scaling/watch-frequency tradeoffs. topology-aware service routing DNS IP list filtering
AI-written summary · about
chapters (4)
related talks
33mCheap Routes, Fast Paths & Keeping Track
27mInside Kubernetes Services
01h 28mSIG-Network Intro & Deep-Dive
42mKubernetes Networking at Scale
36mBack to basics, getting traffic into your Kubernetes cluster
09mMulti-Cluster Networking: A Technology-Agnostic Network Operator for K8 Federation
32mThe Easy--Don't Drive Yourself Crazy--Way to Kubernetes Networking
28mMulti-Cluster Service Mesh With Istio
