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

removed caveat for 1.5 rolling update (#9270)

Browse Source
This commit is contained in:
Deirdre Storck
2018-06-28 11:06:21 -07:00
committed by k8s-ci-robot
parent fbbc4ec15e
commit 5da5c49950
1 changed files with 0 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/manage-daemon/update-daemon-set.md
-11
View File
@@ -34,17 +34,6 @@ DaemonSet has two update strategy types:
DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods 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.
## Caveat: Updating DaemonSet created from Kubernetes version 1.5 or before
If you try a rolling update on a DaemonSet that was created from Kubernetes
version 1.5 or before, a rollout will be triggered when you *first* change the
DaemonSet update strategy to `RollingUpdate`, no matter if DaemonSet template is
modified or not. If the DaemonSet template is not changed, all existing DaemonSet
pods will be restarted (deleted and created).
Therefore, make sure you want to trigger a rollout before you first switch the
strategy to `RollingUpdate`.
## Performing a Rolling Update ## Performing a Rolling Update
To enable the rolling update feature of a DaemonSet, you must set its To enable the rolling update feature of a DaemonSet, you must set its