Modify node pressure expulsion link

Signed-off-by: pangqing <pangqing@uniontech.com>
2022-03-01 10:50:32 +08:00
parent bff6d62c45
commit cdde38b85a
6 changed files with 59 additions and 6 deletions
@@ -49,5 +49,5 @@ of terminating one or more Pods on Nodes.
 ## Pod 干扰

 * [Pod 优先级和抢占](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
-* [节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)
+* [节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 * [API发起的驱逐](/zh/docs/concepts/scheduling-eviction/api-eviction/)
@@ -637,7 +637,7 @@ exceeding its requests, it won't be evicted. Another Pod with higher priority
 that exceeds its requests may be evicted.
 -->
 kubelet 使用优先级来确定
-[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/) Pod 的顺序。
+[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/) Pod 的顺序。
 你可以使用 QoS 类来估计 Pod 最有可能被驱逐的顺序。kubelet 根据以下因素对 Pod 进行驱逐排名：

  1. 对紧俏资源的使用是否超过请求值
@@ -664,4 +664,4 @@ kubelet 使用优先级来确定
  [默认限制优先级消费](/zh/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default)
 * 了解 [Pod 干扰](/zh/docs/concepts/workloads/pods/disruptions/)
 * 了解 [API 发起的驱逐](/docs/reference/generated/kubernetes-api/v1.23/)
-* 了解[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)
+* 了解[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
@@ -545,5 +545,5 @@ arbitrary tolerations to DaemonSets.
 * Read about [Node-pressure Eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/) and how you can configure it
 * Read about [Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 -->
-* 阅读[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)，以及如何配置其行为
+* 阅读[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)，以及如何配置其行为
 * 阅读 [Pod 优先级](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
@@ -33,6 +33,6 @@ There are two kinds of eviction:
 * [API-initiated eviction](/docs/reference/generated/kubernetes-api/v1.23/)
 -->
 驱逐的两种类型
-* [节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)
+* [节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 * [API 发起的驱逐](/docs/reference/generated/kubernetes-api/v1.23/)

@@ -340,7 +340,7 @@ respectively.
 `kubelet` 默认对 Pod 执行 'Allocatable' 约束。
 无论何时，如果所有 Pod 的总用量超过了 'Allocatable'，驱逐 Pod 的措施将被执行。
 有关驱逐策略的更多细节可以在
-[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)页找到。
+[节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)页找到。
 可通过设置 kubelet `--enforce-node-allocatable` 标志值为 `pods` 控制这个措施。

 可选地，通过在同一标志中同时指定 `kube-reserved` 和 `system-reserved` 值，