From c04ffcdce813a764aa5354fec2bba2cf742c4ac6 Mon Sep 17 00:00:00 2001 From: Abhishek Jaisingh Date: Tue, 3 Mar 2020 22:53:38 +0530 Subject: [PATCH] Clarify At-Most-One Semantic For DaemonSet Update (#19283) * Clarify At-Most-One Semantic For DaemonSet Update Make it explicit, that at most one pod will run on each node while updating a daemonset. As mentioned here: https://github.com/kubernetes/kubernetes/issues/48841 * Clarify Update Strategy For DaemonSet Pods Only --- content/en/docs/tasks/manage-daemon/update-daemon-set.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/manage-daemon/update-daemon-set.md b/content/en/docs/tasks/manage-daemon/update-daemon-set.md index 0c1a5472b6..ab98f2ea4e 100644 --- a/content/en/docs/tasks/manage-daemon/update-daemon-set.md +++ b/content/en/docs/tasks/manage-daemon/update-daemon-set.md @@ -33,7 +33,7 @@ DaemonSet has two update strategy types: * RollingUpdate: This is the default update strategy. With `RollingUpdate` update strategy, after you update a DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods - will be created automatically, in a controlled fashion. + will be created automatically, in a controlled fashion. At most one pod of the DaemonSet will be running on each node during the whole update process. ## Performing a Rolling Update