zh-trans: add kube-scheduler.md (#11325)
* zh-trans: add kube-scheduler.md 未解决引入英文原文(#11311)导致的冲突,重新创建PR:#11298 * Update kube-scheduler.md
This commit is contained in:
@@ -3,6 +3,21 @@ title: kube-scheduler
|
|||||||
id: kube-scheduler
|
id: kube-scheduler
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /docs/reference/generated/kube-scheduler/
|
full_link: /docs/reference/generated/kube-scheduler/
|
||||||
|
short_description: >
|
||||||
|
主节点上的组件,该组件监视那些新创建的未指定运行节点的 Pod,并选择节点让 Pod 在上面运行。
|
||||||
|
|
||||||
|
aka:
|
||||||
|
tags:
|
||||||
|
- architecture
|
||||||
|
- scheduler
|
||||||
|
---
|
||||||
|
|
||||||
|
<!--
|
||||||
|
---
|
||||||
|
title: kube-scheduler
|
||||||
|
id: kube-scheduler
|
||||||
|
date: 2018-04-12
|
||||||
|
full_link: /docs/reference/generated/kube-scheduler/
|
||||||
short_description: >
|
short_description: >
|
||||||
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
||||||
|
|
||||||
@@ -10,9 +25,18 @@ aka:
|
|||||||
tags:
|
tags:
|
||||||
- architecture
|
- architecture
|
||||||
---
|
---
|
||||||
|
-->
|
||||||
|
|
||||||
|
<!--
|
||||||
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
||||||
|
-->
|
||||||
|
|
||||||
|
主节点上的组件,该组件监视那些新创建的未指定运行节点的 Pod,并选择节点让 Pod 在上面运行。
|
||||||
|
|
||||||
<!--more-->
|
<!--more-->
|
||||||
|
|
||||||
|
<!--
|
||||||
Factors taken into account for scheduling decisions include individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
|
Factors taken into account for scheduling decisions include individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
|
||||||
|
-->
|
||||||
|
|
||||||
|
调度决策考虑的因素包括单个 Pod 和 Pod 集合的资源需求、硬件/软件/策略约束、亲和性和反亲和性规范、数据位置、工作负载间的干扰和最后时限。
|
||||||
|
|||||||
Reference in New Issue
Block a user