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

Merge pull request #30331 from renan/MaxSurgeDefault

Browse Source 
Fix default value for MaxSurge in RollingUpdates for DaemonSets beat feature
This commit is contained in:
Kubernetes Prow Robot
2022-01-17 13:12:49 -08:00
committed by GitHub
parent d9edcc33ff 696027ce06
commit 9bdb086f30
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/manage-daemon/update-daemon-set.md
+1 -1
View File
@@ -40,7 +40,7 @@ You may want to set
[`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds)
(default to 0) and (default to 0) and
[`.spec.maxSurge`](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-surge) [`.spec.maxSurge`](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-surge)
(a beta feature and defaults to 25%) as well. (a beta feature and defaults to 0) as well.
### Creating a DaemonSet with `RollingUpdate` update strategy ### Creating a DaemonSet with `RollingUpdate` update strategy