Skip to content

Commit f291c08

Browse files
authored
Merge pull request #25654 from guzj11/patch-46
Update update-daemon-set.md
2 parents 0895480 + ba84d93 commit f291c08

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

content/zh/docs/tasks/manage-daemon/update-daemon-set.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -234,6 +234,17 @@ daemonset "fluentd-elasticsearch" successfully rolled out
234234

235235
### DaemonSet 滚动更新卡住
236236

237+
<!--
238+
Sometimes, a DaemonSet rolling update may be stuck. Here are some possible
239+
causes:
240+
241+
#### Some nodes run out of resources
242+
-->
243+
有时,DaemonSet 滚动更新可能卡住,以下是一些可能的原因:
244+
245+
246+
#### 一些节点可用资源耗尽
247+
237248
<!--
238249
The rollout is stuck because new DaemonSet pods can't be scheduled on at least one
239250
node. This is possible when the node is
@@ -242,7 +253,7 @@ node. This is possible when the node is
242253
When this happens, find the nodes that don't have the DaemonSet pods scheduled on
243254
by comparing the output of `kubectl get nodes` and the output of:
244255
-->
245-
有时,DaemonSet 滚动更新可能会卡住,其 Pod 至少在某个节点上无法调度运行。
256+
DaemonSet 滚动更新可能会卡住,其 Pod 至少在某个节点上无法调度运行。
246257
当节点上[可用资源耗尽](/zh/docs/tasks/administer-cluster/out-of-resource/)时,
247258
这是可能的。
248259

0 commit comments

Comments
 (0)