kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update update-daemon-set.md (#10290) 

The default strategy for the update changed from 'OnDelete' to 'RollingUpdate' since Kubernetes 1.8:
https://v1-8.docs.kubernetes.io/docs/api-reference/v1.8/#daemonsetupdatestrategy-v1beta2-apps
pull/10419/merge
caberdoz 2018-10-04 04:31:07 +02:00 committed by k8s-ci-robot
parent 32fdce6f64
commit ade133f06d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/en/docs/tasks/manage-daemon/update-daemon-set.md
View File

@ -25,12 +25,12 @@ This page shows how to perform a rolling update on a DaemonSet.
DaemonSet has two update strategy types:
* OnDelete: This is the default update strategy for backward-compatibility. With
`OnDelete` update strategy, after you update a DaemonSet template, new
* OnDelete: With `OnDelete` update strategy, after you update a DaemonSet template, new
DaemonSet pods will *only* be created when you manually delete old DaemonSet
pods. This is the same behavior of DaemonSet in Kubernetes version 1.5 or
before.
* RollingUpdate: With `RollingUpdate` update strategy, after you update a
* 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.