@@ -64,16 +64,16 @@ write your own scheduling component and use that instead.
64
64
在设计上允许你自己编写一个调度组件并替换原有的 kube-scheduler。
65
65
66
66
<!--
67
- For every newly created pods or other unscheduled pods, kube-scheduler
68
- selects a optimal node for them to run on. However, every container in
69
- pods has different requirements for resources and every pod also has
70
- different requirements. Therefore, existing nodes need to be filtered
71
- according to the specific scheduling requirements.
72
- -->
73
- 对每一个新创建的 Pod 或者是未被调度的 Pod,kube-scheduler 会选择一个最优的节点去运行这个 Pod。
74
- 然而,Pod 内的每一个容器对资源都有不同的需求,
75
- 而且 Pod 本身也有不同的需求。因此, Pod 在被调度到节点上之前,
76
- 根据这些特定的调度需求,需要对集群中的节点进行一次过滤 。
67
+ Kube-scheduler selects an optimal node to run newly created or not yet
68
+ scheduled (unscheduled) pods. Since containers in pods - and pods themselves -
69
+ can have different requirements, the scheduler filters out any nodes that
70
+ don't meet a Pod's specific scheduling needs. Alternatively, the API lets
71
+ you specify a node for a Pod when you create it, but this is unusual
72
+ and is only done in special cases.
73
+ -->
74
+ Kube-scheduler 选择一个最佳节点来运行新创建的或尚未调度(unscheduled)的 Pod。
75
+ 由于 Pod 中的容器和 Pod 本身可能有不同的要求,调度程序会过滤掉任何不满足 Pod 特定调度需求的节点。
76
+ 或者,API 允许你在创建 Pod 时为它指定一个节点,但这并不常见,并且仅在特殊情况下才会这样做 。
77
77
78
78
<!--
79
79
In a cluster, Nodes that meet the scheduling requirements for a Pod
0 commit comments