Node taint management¶
Taint can make a node exclude a certain type of Pod and prevent Pod from being scheduled on the node. One or more taints can be applied to each node, and Pods that cannot tolerate these taints will not be scheduled on that node. For more details about taints, refer to the official Kubernetes documentation Taints and Tolerance.
Precautions¶
- The current operating user should have
NS Edit
role authorization or other higher permissions. - After adding a taint to a node, only Pods that can tolerate the taint can be scheduled to the node.
Steps¶
-
Find the target cluster on the
Cluster List
page, and click the cluster name to enter theCluster Overview
page. -
In the left navigation bar, click
Node Management
, find the node that needs to modify the taint, click theⵗ
operation icon on the right and click theModify taint
button. -
Enter the key value information of the stain in the pop-up box, select the stain effect, and click
OK
.Click
➕ Add
to add multiple stains to the node, and clickX
on the right side of the stain effect to delete the stain.Currently supports three stain effects:
- NoSchedule: Pods that cannot tolerate a taint will not be scheduled on nodes with the taint.
- PreferNoSchedule: Try to avoid Pods that cannot tolerate a taint will not be scheduled on nodes with the taint.
- NoExecute: Keep the status quo. Pods that cannot tolerate a taint will not be evicted if they were already running on the node before the taint was set. Pods that cannot tolerate a taint will not be scheduled on the node if they were not running on the node before the taint was set on the node.