Skip to content

Commit de0efc1

Browse files
authored
Merge pull request #47424 from my-git9/pp-28848
[zh-cn] sync pods/disruptions.md
2 parents f91e87c + a3ebef6 commit de0efc1

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

content/zh-cn/docs/concepts/workloads/pods/disruptions.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -508,6 +508,16 @@ Taint Manager(`kube-controller-manager` 中节点生命周期控制器的一
508508
由于{{<glossary_tooltip term_id="node-pressure-eviction" text="节点压力驱逐">}}或[节点体面关闭](/zh-cn/docs/concepts/architecture/nodes/#graceful-node-shutdown)而被
509509
kubelet 终止。
510510

511+
<!--
512+
In all other disruption scenarios, like eviction due to exceeding
513+
[Pod container limits](/docs/concepts/configuration/manage-resources-containers/),
514+
Pods don't receive the `DisruptionTarget` condition because the disruptions were
515+
probably caused by the Pod and would reoccur on retry.
516+
-->
517+
在所有其他中断场景中,例如由于超出
518+
[Pod 容器限制]而被驱逐,`DisruptionTarget` 状况不会被添加到 Pod 上,
519+
因为中断可能是由 Pod 引起的,并且会在重试时再次发生。
520+
511521
{{< note >}}
512522
<!--
513523
A Pod disruption might be interrupted. The control plane might re-attempt to

0 commit comments

Comments
 (0)