From ade133f06d1cf0f2c3f2225ab8d41a93eb2d583a Mon Sep 17 00:00:00 2001 From: caberdoz Date: Thu, 4 Oct 2018 04:31:07 +0200 Subject: [PATCH] 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 --- content/en/docs/tasks/manage-daemon/update-daemon-set.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 a8a256c4829..d2cd15cdcdc 100644 --- a/content/en/docs/tasks/manage-daemon/update-daemon-set.md +++ b/content/en/docs/tasks/manage-daemon/update-daemon-set.md @@ -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.