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

wrap contents by shortcodes (#10058)

Browse Source
This commit is contained in:
makocchi
2018-08-24 03:28:40 +09:00
committed by k8s-ci-robot
parent 1b69db5c92
commit 490dc84413
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/taint-and-toleration.md
+9 -3
View File
@@ -69,7 +69,8 @@ A toleration "matches" a taint if the keys are the same and the effects are the
`Operator` defaults to `Equal` if not specified. `Operator` defaults to `Equal` if not specified.
**NOTE:** There are two special cases: {{< note >}}
**Note:** There are two special cases:
* An empty `key` with operator `Exists` matches all keys, values and effects which means this * An empty `key` with operator `Exists` matches all keys, values and effects which means this
will tolerate everything. will tolerate everything.
@@ -86,6 +87,7 @@ tolerations:
- key: "key" - key: "key"
operator: "Exists" operator: "Exists"
``` ```
{{< /note >}}
The above example used `effect` of `NoSchedule`. Alternatively, you can use `effect` of `PreferNoSchedule`. The above example used `effect` of `NoSchedule`. Alternatively, you can use `effect` of `PreferNoSchedule`.
This is a "preference" or "soft" version of `NoSchedule` -- the system will *try* to avoid placing a This is a "preference" or "soft" version of `NoSchedule` -- the system will *try* to avoid placing a
@@ -227,10 +229,14 @@ including `TaintBasedEvictions=true` in `--feature-gates` for Kubernetes control
such as `--feature-gates=FooBar=true,TaintBasedEvictions=true`), the taints are automatically such as `--feature-gates=FooBar=true,TaintBasedEvictions=true`), the taints are automatically
added by the NodeController (or kubelet) and the normal logic for evicting pods from nodes added by the NodeController (or kubelet) and the normal logic for evicting pods from nodes
based on the Ready NodeCondition is disabled. based on the Ready NodeCondition is disabled.
(Note: To maintain the existing [rate limiting](/docs/concepts/architecture/nodes/)
{{< note >}}
**Note:** To maintain the existing [rate limiting](/docs/concepts/architecture/nodes/)
behavior of pod evictions due to node problems, the system actually adds the taints behavior of pod evictions due to node problems, the system actually adds the taints
in a rate-limited way. This prevents massive pod evictions in scenarios such in a rate-limited way. This prevents massive pod evictions in scenarios such
as the master becoming partitioned from the nodes.) as the master becoming partitioned from the nodes.
{{< /note >}}
This alpha feature, in combination with `tolerationSeconds`, allows a pod This alpha feature, in combination with `tolerationSeconds`, allows a pod
to specify how long it should stay bound to a node that has one or both of these problems. to specify how long it should stay bound to a node that has one or both of these problems.