Tolerance Policies

A tolerance policy allows the scheduler to schedule pods to nodes with corresponding taints. This policy must be used together with node taints. One or more taints can be added to each node. For pods without node tolerance policy, the scheduler performs selective scheduling based on the taint effect to prevent pods from being allocated to inappropriate nodes.

Configuring a Tolerance Policy on the Console

1. Log in to the UCS console.
2. When creating a workload, click Next: Scheduling and Differentiation.
3. Add a tolerance policy.

   Parameter	Description
   Taint Key	Key of a node taint.
   Operator	Equal: matches the nodes with the specified taint key (mandatory) and value. If the taint value is left blank, all taints with the key the same as the specified taint key will be matched. Exists: matches the nodes with the specified taint key. In this case, the taint value cannot be specified. If the taint key is left blank, all taints will be tolerated.
   Taint Value	If the value of Operator is Exists, the value attribute can be omitted. If the value of Operator is Equal, the relationship between the key and value is Equal. If Operator is not specified, the default value is Equal.
   Taint Policy	All: All taint policies are matched. NoSchedule: Only the NoSchedule taint is matched. NoExecute: Only the NoExecute taint is matched.
   Toleration Time Window	tolerationSeconds, which is configurable only when Taint Policy is set to NoExecute. Within the tolerance time window, pods still run on the node with taints. After the time expires, the pods will be evicted.