From 06599a6259da505a152ac136bd93204d51c5469c Mon Sep 17 00:00:00 2001 From: ravisantoshgudimetla Date: Wed, 14 Jul 2021 10:58:21 -0400 Subject: [PATCH] Make maxSurge as beta feature for DaemonSets kubernetes/kubernetes#101742 merged which made this feature beta. This is the companion docs PR for kubernetes/enhancements#2665 Co-authored-by: Karen Bradshaw --- .../en/docs/tasks/manage-daemon/update-daemon-set.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 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 e7b32d9b3f..9f245ac549 100644 --- a/content/en/docs/tasks/manage-daemon/update-daemon-set.md +++ b/content/en/docs/tasks/manage-daemon/update-daemon-set.md @@ -32,11 +32,13 @@ DaemonSet has two update strategy types: 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. +You may want to set +[`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/concepts/workloads/controllers/deployment/#max-unavailable) +(default to 1), +[`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) +(default to 0) and +[`.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