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

added link to spec.minReadySeconds and maxUnavailable for clarity (#9194)

Browse Source 
* added link to minReadySeconds

* link for max unavailable

* used relative path
This commit is contained in:
Deirdre Storck
2018-06-29 18:37:20 -07:00
committed by k8s-ci-robot
parent e0dd309c4e
commit 16b00693fc
1 changed files with 22 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/manage-daemon/update-daemon-set.md
+2 -5
View File
@@ -39,8 +39,8 @@ DaemonSet has two update strategy types:
To enable the rolling update feature of a DaemonSet, you must set its To enable the rolling update feature of a DaemonSet, you must set its
`.spec.updateStrategy.type` to `RollingUpdate`. `.spec.updateStrategy.type` to `RollingUpdate`.
You may want to set `.spec.updateStrategy.rollingUpdate.maxUnavailable` (default You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/concepts/workloads/controllers/deployment/#max-unavailable) (default
to 1) and `.spec.minReadySeconds` (default to 0) as well. to 1) and [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) (default to 0) as well.
### Step 1: Checking DaemonSet `RollingUpdate` update strategy ### Step 1: Checking DaemonSet `RollingUpdate` update strategy
@@ -191,6 +191,3 @@ progress.
* See [Concepts: Creating a DaemonSet to adopt existing DaemonSet pods](/docs/concepts/workloads/controllers/daemonset/) * See [Concepts: Creating a DaemonSet to adopt existing DaemonSet pods](/docs/concepts/workloads/controllers/daemonset/)
{{% /capture %}} {{% /capture %}}