Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[zh-cn] sync pods/disruptions.md #47424

Merged
merged 1 commit into from
Aug 10, 2024
Merged

[zh-cn] sync pods/disruptions.md #47424

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions content/zh-cn/docs/concepts/workloads/pods/disruptions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -508,6 +508,16 @@ Taint Manager（`kube-controller-manager` 中节点生命周期控制器的一
由于{{<glossary_tooltip term_id="node-pressure-eviction" text="节点压力驱逐">}}或[节点体面关闭](/zh-cn/docs/concepts/architecture/nodes/#graceful-node-shutdown)而被
kubelet 终止。

<!--
In all other disruption scenarios, like eviction due to exceeding
[Pod container limits](/docs/concepts/configuration/manage-resources-containers/),
Pods don't receive the `DisruptionTarget` condition because the disruptions were
probably caused by the Pod and would reoccur on retry.
-->
在所有其他中断场景中，例如由于超出
[Pod 容器限制]而被驱逐，`DisruptionTarget` 状况不会被添加到 Pod 上，
因为中断可能是由 Pod 引起的，并且会在重试时再次发生。

{{< note >}}
<!--
A Pod disruption might be interrupted. The control plane might re-attempt to
Expand Down