申请试用
HOT
登录
注册
 
Topology-aware Service Routing in Kubernetes Boots

Topology-aware Service Routing in Kubernetes Boots

圆圆
/
发布于
/
2551
人观看
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.
1 点赞
0 收藏
0下载
确认
3秒后跳转登录页面
去登陆