Merge pull request #28176 from chenrui333/zh/resync-scheduling-eviction-files

zh: resync scheduling files

Author: k8s-ci-robot

content/zh/docs/concepts/scheduling-eviction/_index.md

@@ -1,5 +1,53 @@
 ---
-title: 调度和驱逐 (Scheduling and Eviction)
+title: 调度，抢占和驱逐
 weight: 90
-description: 在Kubernetes中，调度 (Scheduling) 指的是确保 Pods 匹配到合适的节点，以便 kubelet 能够运行它们。驱逐 (Eviction) 是在资源匮乏的节点上，主动让一个或多个 Pods 失效的过程。
+content_type: concept
+description: >
+  在Kubernetes中，调度 (scheduling) 指的是确保 Pods 匹配到合适的节点，
+  以便 kubelet 能够运行它们。抢占 (Preemption) 指的是终止低优先级的 Pods 以便高优先级的 Pods 可以
+  调度运行的过程。驱逐 (Eviction) 是在资源匮乏的节点上，主动让一个或多个 Pods 失效的过程。
 ---
+
+<!--
+---
+title: "Scheduling, Preemption and Eviction"
+weight: 90
+content_type: concept
+description: >
+  In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes
+  so that the kubelet can run them. Preemption is the process of terminating
+  Pods with lower Priority so that Pods with higher Priority can schedule on
+  Nodes. Eviction is the process of proactively terminating one or more Pods on
+  resource-starved Nodes.
+no_list: true
+---
+-->
+
+<!--
+In Kubernetes, scheduling refers to making sure that {{<glossary_tooltip text="Pods" term_id="pod">}}
+are matched to {{<glossary_tooltip text="Nodes" term_id="node">}} so that the
+{{<glossary_tooltip text="kubelet" term_id="kubelet">}} can run them. Preemption
+is the process of terminating Pods with lower {{<glossary_tooltip text="Priority" term_id="pod-priority">}}
+so that Pods with higher Priority can schedule on Nodes. Eviction is the process
+of terminating one or more Pods on Nodes.
+-->
+
+<!-- ## Scheduling -->
+
+## 调度
+
+* [Kubernetes 调度器](/zh/docs/concepts/scheduling-eviction/kube-scheduler/)
+* [将 Pods 指派到节点](/zh/docs/concepts/scheduling-eviction/assign-pod-node/)
+* [Pod 开销](/zh/docs/concepts/scheduling-eviction/pod-overhead/)
+* [污点和容忍](/zh/docs/concepts/scheduling-eviction/taint-and-toleration/)
+* [调度框架](/zh/docs/concepts/scheduling-eviction/scheduling-framework)
+* [调度器的性能调试](/zh/docs/concepts/scheduling-eviction/scheduler-perf-tuning/)
+* [扩展资源的资源装箱](/zh/docs/concepts/scheduling-eviction/resource-bin-packing/)
+
+<!-- ## Pod Disruption -->
+
+## Pod 干扰
+
+* [Pod 优先级和抢占](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
+* [节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)
+* [API发起的驱逐](/zh/docs/concepts/scheduling-eviction/api-eviction/)

content/zh/docs/concepts/scheduling-eviction/assign-pod-node.md

@@ -75,9 +75,9 @@ Run `kubectl get nodes` to get the names of your cluster's nodes. Pick out the o
 
 执行 `kubectl get nodes` 命令获取集群的节点名称。
 选择一个你要增加标签的节点，然后执行
-`kubectl label nodes <node-name> <label-key>=<label-value>` 
+`kubectl label nodes <node-name> <label-key>=<label-value>`
 命令将标签添加到你所选择的节点上。
-例如，如果你的节点名称为 'kubernetes-foo-node-1.c.a-robinson.internal' 
+例如，如果你的节点名称为 'kubernetes-foo-node-1.c.a-robinson.internal'
 并且想要的标签是 'disktype=ssd'，则可以执行
 `kubectl label nodes kubernetes-foo-node-1.c.a-robinson.internal disktype=ssd` 命令。
 
@@ -136,8 +136,18 @@ with a standard set of labels. See [Well-Known Labels, Annotations and Taints](/
 -->
 ## 插曲：内置的节点标签 {#built-in-node-labels}
 
-除了你[添加](#attach-labels-to-node)的标签外，节点还预先填充了一组标准标签。
-参见[常用标签、注解和污点](/zh/docs/reference/labels-annotations-taints/)。
+除了你[添加](#step-one-attach-label-to-the-node)的标签外，节点还预制了一组标准标签。
+参见这些[常用的标签，注解以及污点](/zh/docs/reference/labels-annotations-taints/)：
+
+* [`kubernetes.io/hostname`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#kubernetes-io-hostname)
+* [`failure-domain.beta.kubernetes.io/zone`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#failure-domainbetakubernetesiozone)
+* [`failure-domain.beta.kubernetes.io/region`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#failure-domainbetakubernetesioregion)
+* [`topology.kubernetes.io/zone`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#topologykubernetesiozone)
+* [`topology.kubernetes.io/region`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#topologykubernetesiozone)
+* [`beta.kubernetes.io/instance-type`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#beta-kubernetes-io-instance-type)
+* [`node.kubernetes.io/instance-type`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#nodekubernetesioinstance-type)
+* [`kubernetes.io/os`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#kubernetes-io-os)
+* [`kubernetes.io/arch`](/zh/docs/reference/kubernetes-api/labels-annotations-taints/#kubernetes-io-arch)
 
 {{< note >}}
 <!--
@@ -181,7 +191,7 @@ To make use of that label prefix for node isolation:
 For example, `example.com.node-restriction.kubernetes.io/fips=true` or `example.com.node-restriction.kubernetes.io/pci-dss=true`.
 -->
 1. 检查是否在使用 Kubernetes v1.11+，以便 NodeRestriction 功能可用。
-2. 确保你在使用[节点授权](/zh/docs/reference/access-authn-authz/node/)并且已经_启用_ 
+2. 确保你在使用[节点授权](/zh/docs/reference/access-authn-authz/node/)并且已经_启用_
    [NodeRestriction 准入插件](/zh/docs/reference/access-authn-authz/admission-controllers/#noderestriction)。
 3. 将 `node-restriction.kubernetes.io/` 前缀下的标签添加到 Node 对象，
    然后在节点选择器中使用这些标签。
@@ -574,7 +584,7 @@ must be satisfied for the pod to be scheduled onto a node.
 <!--
 Users can also select matching namespaces using `namespaceSelector`, which is a label query over the set of namespaces.
 The affinity term is applied to the union of the namespaces selected by `namespaceSelector` and the ones listed in the `namespaces` field.
-Note that an empty `namespaceSelector` ({}) matches all namespaces, while a null or empty `namespaces` list and 
+Note that an empty `namespaceSelector` ({}) matches all namespaces, while a null or empty `namespaces` list and
 null `namespaceSelector` means "this pod's namespace".
 -->
 用户也可以使用 `namespaceSelector` 选择匹配的名字空间，`namespaceSelector`
@@ -828,4 +838,3 @@ resource allocation decisions.
 一旦 Pod 分配给 节点，kubelet 应用将运行该 pod 并且分配节点本地资源。
 [拓扑管理器](/zh/docs/tasks/administer-cluster/topology-manager/)
 可以参与到节点级别的资源分配决定中。
-

content/zh/docs/concepts/scheduling-eviction/pod-overhead.md

@@ -1,9 +1,21 @@
 ---
 title: Pod 开销
 content_type: concept
-weight: 20
+weight: 30
 ---
 
+<!--
+---
+reviewers:
+- dchen1107
+- egernst
+- tallclair
+title: Pod Overhead
+content_type: concept
+weight: 30
+---
+-->
+
 <!-- overview -->
 
 {{< feature-state for_k8s_version="v1.18" state="beta" >}}
@@ -58,7 +70,7 @@ across your cluster, and a `RuntimeClass` is utilized which defines the `overhea
 您需要确保在集群中启用了 `PodOverhead` [特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/)
 （在 1.18 默认是开启的），以及一个用于定义 `overhead` 字段的 `RuntimeClass`。
 
-<!-- 
+<!--
 ## Usage example
 -->
 ## 使用示例
@@ -85,7 +97,7 @@ overhead:
         cpu: "250m"
 ```
 
-<!-- 
+<!--
 Workloads which are created which specify the `kata-fc` RuntimeClass handler will take the memory and
 cpu overheads into account for resource quota calculations, node scheduling, as well as Pod cgroup sizing.
 
@@ -119,7 +131,7 @@ spec:
         memory: 100Mi
 ```
 
-<!-- 
+<!--
 At admission time the RuntimeClass [admission controller](/docs/reference/access-authn-authz/admission-controllers/)
 updates the workload's PodSpec to include the `overhead` as described in the RuntimeClass. If the PodSpec already has this field defined,
 the Pod will be rejected. In the given example, since only the RuntimeClass name is specified, the admission controller mutates the Pod
@@ -129,7 +141,7 @@ to include an `overhead`.
  RuntimeClass 中定义的 `overhead`. 如果 PodSpec 中该字段已定义，该 Pod 将会被拒绝。
 在这个例子中，由于只指定了 RuntimeClass 名称，所以准入控制器更新了 Pod, 包含了一个 `overhead`.
 
-<!-- 
+<!--
 After the RuntimeClass admission controller, you can check the updated PodSpec:
 -->
 在 RuntimeClass 准入控制器之后，可以检验一下已更新的 PodSpec:
@@ -138,33 +150,33 @@ After the RuntimeClass admission controller, you can check the updated PodSpec:
 kubectl get pod test-pod -o jsonpath='{.spec.overhead}'
 ```
 
-<!-- 
+<!--
 The output is:
 -->
 输出：
 ```
 map[cpu:250m memory:120Mi]
 ```
 
-<!-- 
+<!--
 If a ResourceQuota is defined, the sum of container requests as well as the
 `overhead` field are counted.
  -->
 如果定义了 ResourceQuata, 则容器请求的总量以及 `overhead` 字段都将计算在内。
 
-<!-- 
+<!--
 When the kube-scheduler is deciding which node should run a new Pod, the scheduler considers that Pod's
 `overhead` as well as the sum of container requests for that Pod. For this example, the scheduler adds the
 requests and the overhead, then looks for a node that has 2.25 CPU and 320 MiB of memory available.
 -->
 当 kube-scheduler 决定在哪一个节点调度运行新的 Pod 时，调度器会兼顾该 Pod 的 `overhead` 以及该 Pod 的容器请求总量。在这个示例中，调度器将资源请求和开销相加，然后寻找具备 2.25 CPU 和 320 MiB 内存可用的节点。
 
-<!-- 
+<!--
 Once a Pod is scheduled to a node, the kubelet on that node creates a new {{< glossary_tooltip text="cgroup" term_id="cgroup" >}}
 for the Pod. It is within this pod that the underlying container runtime will create containers. -->
 一旦 Pod 调度到了某个节点， 该节点上的 kubelet 将为该 Pod 新建一个 {{< glossary_tooltip text="cgroup" term_id="cgroup" >}}. 底层容器运行时将在这个 pod 中创建容器。
 
-<!-- 
+<!--
 If the resource has a limit defined for each container (Guaranteed QoS or Bustrable QoS with limits defined),
 the kubelet will set an upper limit for the pod cgroup associated with that resource (cpu.cfs_quota_us for CPU
 and memory.limit_in_bytes memory). This upper limit is based on the sum of the container limits plus the `overhead`
@@ -179,31 +191,31 @@ requests plus the `overhead` defined in the PodSpec.
 -->
 对于 CPU, 如果 Pod 的 QoS 是 Guaranteed 或者 Burstable, kubelet 会基于容器请求总量与 PodSpec 中定义的 `overhead` 之和设置 `cpu.shares`.
 
-<!-- 
+<!--
 Looking at our example, verify the container requests for the workload:
 -->
 请看这个例子，验证工作负载的容器请求：
 ```bash
 kubectl get pod test-pod -o jsonpath='{.spec.containers[*].resources.limits}'
 ```
 
-<!-- 
+<!--
 The total container requests are 2000m CPU and 200MiB of memory:
 -->
 容器请求总计 2000m CPU 和 200MiB 内存：
 ```
 map[cpu: 500m memory:100Mi] map[cpu:1500m memory:100Mi]
 ```
 
-<!-- 
+<!--
 Check this against what is observed by the node:
  -->
 对照从节点观察到的情况来检查一下：
 ```bash
 kubectl describe node | grep test-pod -B2
 ```
 
-<!-- 
+<!--
 The output shows 2250m CPU and 320MiB of memory are requested, which includes PodOverhead:
  -->
 该输出显示请求了 2250m CPU 以及 320MiB 内存，包含了 PodOverhead 在内：
@@ -226,8 +238,9 @@ cgroups directly on the node.
 
 First, on the particular node, determine the Pod identifier:
 -->
-在工作负载所运行的节点上检查 Pod 的内存 cgroups. 在接下来的例子中，将在该节点上使用具备 CRI 兼容的容器运行时命令行工具 [`crictl`](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md). 
-这是一个展示 PodOverhead 行为的进阶示例，用户并不需要直接在该节点上检查 cgroups.
+在工作负载所运行的节点上检查 Pod 的内存 cgroups. 在接下来的例子中，
+将在该节点上使用具备 CRI 兼容的容器运行时命令行工具
+[`crictl`](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md)。
 
 首先在特定的节点上确定该 Pod 的标识符：
 
@@ -240,7 +253,7 @@ First, on the particular node, determine the Pod identifier:
 POD_ID="$(sudo crictl pods --name test-pod -q)"
 ```
 
-<!-- 
+<!--
 From this, you can determine the cgroup path for the Pod:
  -->
 可以依此判断该 Pod 的 cgroup 路径：
@@ -254,15 +267,15 @@ From this, you can determine the cgroup path for the Pod:
 sudo crictl inspectp -o=json $POD_ID | grep cgroupsPath
 ```
 
-<!-- 
+<!--
 The resulting cgroup path includes the Pod's `pause` container. The Pod level cgroup is one directory above.
 -->
 执行结果的 cgroup 路径中包含了该 Pod 的 `pause` 容器。Pod 级别的 cgroup 即上面的一个目录。
 ```
         "cgroupsPath": "/kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2/7ccf55aee35dd16aca4189c952d83487297f3cd760f1bbf09620e206e7d0c27a"
 ```
 
-<!-- 
+<!--
 In this specific case, the pod cgroup path is `kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2`. Verify the Pod level cgroup setting for memory:
  -->
 在这个例子中，该 pod 的 cgroup 路径是 `kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2`。验证内存的 Pod 级别 cgroup 设置：
@@ -278,15 +291,15 @@ In this specific case, the pod cgroup path is `kubepods/podd7f4b509-cf94-4951-94
  cat /sys/fs/cgroup/memory/kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2/memory.limit_in_bytes
 ```
 
-<!-- 
+<!--
 This is 320 MiB, as expected:
 -->
 和预期的一样是 320 MiB
 ```
 335544320
 ```
 
-<!-- 
+<!--
 ### Observability
 -->
 ### 可观察性
@@ -298,8 +311,11 @@ running with a defined Overhead. This functionality is not available in the 1.9
 kube-state-metrics, but is expected in a following release. Users will need to build kube-state-metrics
 from source in the meantime.
 -->
-在 [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) 中可以通过 `kube_pod_overhead` 指标来协助确定何时使用 PodOverhead 以及协助观察以一个既定开销运行的工作负载的稳定性。
-该特性在 kube-state-metrics 的 1.9 发行版本中不可用，不过预计将在后续版本中发布。在此之前，用户需要从源代码构建 kube-state-metrics. 
+在 [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) 中可以通过
+`kube_pod_overhead` 指标来协助确定何时使用 PodOverhead 以及协助观察以一个既定
+开销运行的工作负载的稳定性。
+该特性在 kube-state-metrics 的 1.9 发行版本中不可用，不过预计将在后续版本中发布。
+在此之前，用户需要从源代码构建 kube-state-metrics。
 
 ## {{% heading "whatsnext" %}}
 
@@ -310,4 +326,3 @@ from source in the meantime.
 
 * [RuntimeClass](/zh/docs/concepts/containers/runtime-class/)
 * [PodOverhead 设计](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/688-pod-overhead)
-

content/zh/docs/concepts/scheduling-eviction/resource-bin-packing.md

@@ -1,24 +1,26 @@
 ---
 title: 扩展资源的资源装箱
 content_type: concept
-weight: 30
+weight: 80
 ---
 <!--
+---
 reviewers:
 - bsalamat
 - k82cn
 - ahg-g
 title: Resource Bin Packing for Extended Resources
 content_type: concept
-weight: 30
+weight: 80
+---
 -->
 
 <!-- overview -->
 
 {{< feature-state for_k8s_version="1.16" state="alpha" >}}
 
 <!--
-The kube-scheduler can be configured to enable bin packing of resources along with extended resources using `RequestedToCapacityRatioResourceAllocation` priority function. Priority functions can be used to fine-tune the kube-scheduler as per custom needs. 
+The kube-scheduler can be configured to enable bin packing of resources along with extended resources using `RequestedToCapacityRatioResourceAllocation` priority function. Priority functions can be used to fine-tune the kube-scheduler as per custom needs.
 -->
 
 使用 `RequestedToCapacityRatioResourceAllocation` 优先级函数，可以将 kube-scheduler
@@ -48,7 +50,7 @@ Kubernetes 1.16 在优先级函数中添加了一个新参数，该参数允许
 （least requested）或
 最多请求（most requested）计算。
 `resources` 包含由 `name` 和  `weight` 组成，`name` 指定评分时要考虑的资源，
-`weight` 指定每种资源的权重。 
+`weight` 指定每种资源的权重。
 
 <!--
 Below is an example configuration that sets `requestedToCapacityRatioArguments` to bin packing behavior for extended resources `intel.com/foo` and `intel.com/bar`
@@ -130,7 +132,7 @@ The above arguments give the node a score of 0 if utilization is 0% and 10 for u
 ```
 
 <!--
-It can be used to add extended resources as follows: 
+It can be used to add extended resources as follows:
 -->
 它可以用来添加扩展资源，如下所示：
 
@@ -249,4 +251,3 @@ CPU            = resourceScoringFunction((2+6),8)
 NodeScore   =  (5 * 5) + (7 * 1) + (10 * 3) / (5 + 1 + 3)
             =  7
 ```
-