- 快召唤伙伴们来围观吧
- 微博 QQ QQ空间 贴吧
- 文档嵌入链接
- 复制
- 微信扫一扫分享
- 已成功复制到剪贴板
Topology-aware Service Routing in Kubernetes Boots
展开查看详情
1 .Topology-aware Service Routing in Kubernetes Boots a Smarter Service Discovery Jun Du, Software Engineer, Huawei Cloud
2 .Agenda Topologies in Kubernetes Topology-aware service routing Solutions and prototypes Q&A
3 .Topology is Arbitrary AZ Region Rack Host Generator Anything you like…
4 .Topology in Kubernets scheduler Scheduling is about finding hardware to run your code. Where should I run this Pod?
5 .Node Affinity Should I run my Pod on this Node?
6 .Pod Affinity/Anti-affinity Labels identify topologies topologyKey is the key of Node Labels Should I run my Pod in the same hostname as a web-frontend Pod?
7 .Topologies in Pod (Anti-)Affinity
8 .
9 .
10 .Supported topology-aware features in Kubernetes Node level - Workloads - Volumes Within a node - Hardware
11 .Agenda Topologies in Kubernetes Requests of topology-aware service routing Solutions and prototypes Q&A
12 .Kubernetes Service & Endpoints
13 .i ptables IPVS
14 .Topology-aware service routing: user stories Clear demand for node-local - per-node services: fluentd , aws - es -proxy - secure “Find zone-local backends for service X”? - data costs - performance Extend: “locality” means same topological level - select a subset of endpoints based on topology
15 .Topology-aware service routing: problem statements Hard requests or soft requests? - try local, then go wider ? - always want that one? How hard to try? - weight per topo What if multiple backends satisfy? - probabilities
16 .Topology-aware service routing: problem statements Hard requests or soft requests? - try local, then go wider ? - always want that one? How hard to try? - weight per topo What if multiple backends satisfy? - probabilities
17 .Solutions and prototypes API Changes:
18 .Architecture
19 .Data Flow
20 .Topology-aware service routing R unning well in Huawei Cloud CCE Happy to open source the implementation - Proposal: https ://github.com/kubernetes/community/pull/1551
21 .Contact US!
22 .Contact US!