It's a pain point for multi-zone clusters deployment since cross-zone network traffic being charged, while in-zone is not. In addition, cross-node traffic may carry sensitive metadata from other nodes. Therefore, users always prefer the service backends that close to them, e.g. same zone, rack and host etc. for security, performance and cost concerns. Kubernetes scheduler can constraining a pod to only be able to run on particular nodes/zones. However, Kubernetes service proxy just randomly picks an available backend for service routing and this one can be very far from the user, so we need a topology-aware service routing solution in Kubernetes. Basically, to find the nearest service backend. This talk will be a deep dive of how Huawei Cloud achieve this sort of topology guarantee in a generic and Kubernetes-native way, no matter what kind of topological level.
Jun Du is one of the CNCF TOC Contributors and the author of two books on cloud-native area, e.g. "docker--containers and cloud”and“etcd in-depth interpretation". He is the maintainer and owner of some notable features of Kubernetes, e.g. IPVS-based kube-proxy and pod traffic... Read More →
