From edcbc900dab7732d281ba41c3cfbd7942fe5ad59 Mon Sep 17 00:00:00 2001 From: Ravi Gudimetla Date: Sun, 23 May 2021 18:19:11 -0400 Subject: [PATCH] Introduce maxSurge as beta feature for DaemonSets https://github.com/kubernetes/kubernetes/pull/101742 merged which made this feature beta. This is the companion docs PR for https://github.com/kubernetes/enhancements/pull/2665 --- content/en/docs/tasks/manage-daemon/update-daemon-set.md | 4 ++-- 1 file changed, 2 insertions(+), 2 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 2f3001da0f1a3..214ce799d592c 100644 --- a/content/en/docs/tasks/manage-daemon/update-daemon-set.md +++ b/content/en/docs/tasks/manage-daemon/update-daemon-set.md @@ -29,13 +29,13 @@ DaemonSet has two update strategy types: DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods 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 +## Performing a Rolling Updatec To enable the rolling update feature of a DaemonSet, you must set its `.spec.updateStrategy.type` to `RollingUpdate`. You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/concepts/workloads/controllers/deployment/#max-unavailable) (default -to 1) and [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) (default to 0) as well. +to 1), [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) (default to 0) [`.spec.maxSurge`](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-surge) (a beta feature and defaults to 25%) as well. ### Creating a DaemonSet with `RollingUpdate` update strategy