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

Fix default value for MaxSurge

Browse Source 
The implementation defines the default value for MaxSurge being 0, as to
preserve the current behavior of rolling updates in DaemonSets.

This change is just a copy-paste of the docblock defined in the types.go
file.

See:
- https://github.com/kubernetes/kubernetes/blob/10a3cc815bea73f78f7126cab5df95233da96e1b/pkg/apis/apps/types.go
- https://github.com/kubernetes/kubernetes/blob/10a3cc815bea73f78f7126cab5df95233da96e1b/pkg/apis/apps/v1/defaults.go#L87-L91
This commit is contained in:
Renan Gonçalves
2021-11-02 14:03:40 +01:00
parent 007f515d17
commit b4b8893a93
3 changed files with 4 additions and 4 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)
(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.
(a beta feature and defaults to 0) as well.
### Creating a DaemonSet with `RollingUpdate` update strategy