All Documents
Current Document
Content is empty
If you don't find the content you expect, please try another search term
Found 0 result in total
Content is empty
If you don't find the content you expect, please try another search term
Last updated：2021-11-11 17:43:13
The node selector and node affinity policies allow you to schedule pods onto the nodes that meet the specified rules. On the contrary, property taints on a node allow it to repel specific pods. You can set pod toleration policies so that pods can be scheduled onto nodes with specific taints. Taints and tolerations can be used together to prevent pods from being scheduled onto inappropriate nodes.
Note
- You can go to the Deployment, StatefulSet, or DaemonSet page as required.
The following table describes the detailed settings of a pod toleration policy.
| Parameter | Description |
|---|---|
| Toleration Key | The key of the taint. If you do not specify this parameter, all taints are included. In this case, you must set the Operator parameter to Exists. |
| Operator | The operator between the key and the value. Valid values: Exists and Equal. |
| Toleration Value | The value of the taint. |
| Effect | The effect of the rule. Valid values: NoSchedule, PreferNoSchedule, and NoExecute. |
| Time (S) | The duration of the toleration. By default, this parameter is left unspecified, which indicates that the pod can permanently tolerate the taint and will not be repelled. If you set this field to 0 or a negative value, the pod will be immediately repelled. |
You can click Add Scheduling Rule to add multiple pod toleration rules. A pod can be scheduled when it meets any of the toleration rules.
Pure Mode
