whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify At-Most-One Semantic For DaemonSet Update (#19283)

Browse Source 
* 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
This commit is contained in:
Abhishek Jaisingh
2020-03-03 22:53:38 +05:30
committed by GitHub
parent 2cfbdac0d5
commit c04ffcdce8
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/manage-daemon/update-daemon-set.md
+1 -1
View File
@@ -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