Merge pull request #25654 from guzj11/patch-46
Update update-daemon-set.md
This commit is contained in:
commit
f291c08872
|
@ -234,6 +234,17 @@ daemonset "fluentd-elasticsearch" successfully rolled out
|
|||
|
||||
### DaemonSet 滚动更新卡住
|
||||
|
||||
<!--
|
||||
Sometimes, a DaemonSet rolling update may be stuck. Here are some possible
|
||||
causes:
|
||||
|
||||
#### Some nodes run out of resources
|
||||
-->
|
||||
有时,DaemonSet 滚动更新可能卡住,以下是一些可能的原因:
|
||||
|
||||
|
||||
#### 一些节点可用资源耗尽
|
||||
|
||||
<!--
|
||||
The rollout is stuck because new DaemonSet pods can't be scheduled on at least one
|
||||
node. This is possible when the node is
|
||||
|
@ -242,7 +253,7 @@ node. This is possible when the node is
|
|||
When this happens, find the nodes that don't have the DaemonSet pods scheduled on
|
||||
by comparing the output of `kubectl get nodes` and the output of:
|
||||
-->
|
||||
有时,DaemonSet 滚动更新可能会卡住,其 Pod 至少在某个节点上无法调度运行。
|
||||
DaemonSet 滚动更新可能会卡住,其 Pod 至少在某个节点上无法调度运行。
|
||||
当节点上[可用资源耗尽](/zh/docs/tasks/administer-cluster/out-of-resource/)时,
|
||||
这是可能的。
|
||||
|
||||
|
|
Loading…
Reference in New Issue