File tree Expand file tree Collapse file tree 1 file changed +12
-1
lines changed
content/zh/docs/tasks/manage-daemon Expand file tree Collapse file tree 1 file changed +12
-1
lines changed Original file line number Diff line number Diff line change @@ -234,6 +234,17 @@ daemonset "fluentd-elasticsearch" successfully rolled out
234
234
235
235
### DaemonSet 滚动更新卡住
236
236
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
+
237
248
<!--
238
249
The rollout is stuck because new DaemonSet pods can't be scheduled on at least one
239
250
node. This is possible when the node is
@@ -242,7 +253,7 @@ node. This is possible when the node is
242
253
When this happens, find the nodes that don't have the DaemonSet pods scheduled on
243
254
by comparing the output of `kubectl get nodes` and the output of:
244
255
-->
245
- 有时, DaemonSet 滚动更新可能会卡住,其 Pod 至少在某个节点上无法调度运行。
256
+ DaemonSet 滚动更新可能会卡住,其 Pod 至少在某个节点上无法调度运行。
246
257
当节点上[ 可用资源耗尽] ( /zh/docs/tasks/administer-cluster/out-of-resource/ ) 时,
247
258
这是可能的。
248
259
You can’t perform that action at this time.
0 commit comments