From ba84d93ebd3beacd2e43a72db0b4350e524def17 Mon Sep 17 00:00:00 2001
From: guzj11 <67083623+guzj11@users.noreply.github.com>
Date: Wed, 16 Dec 2020 14:34:05 +0800
Subject: [PATCH] t # This is a combination of 3 commits.

Update update-daemon-set.md

sync with english version.

Update update-daemon-set.md

apply suggestion

Update update-daemon-set.md

apply suggestion
---
 .../docs/tasks/manage-daemon/update-daemon-set.md   | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/content/zh/docs/tasks/manage-daemon/update-daemon-set.md b/content/zh/docs/tasks/manage-daemon/update-daemon-set.md
index 6d425f4d51..15631cf688 100644
--- a/content/zh/docs/tasks/manage-daemon/update-daemon-set.md
+++ b/content/zh/docs/tasks/manage-daemon/update-daemon-set.md
@@ -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/)时，
 这是可能的。