Platform Center
Home / Platform management / Clusters / Clusters / Node management / Management node

Management node

Support updating node labels, adding or deleting custom node labels.

Update node labels

Labels are key-value pairs attached to nodes that define their attributes. Setting labels on nodes makes it easy to filter or select nodes based on their labels. For example, directing a pod to be scheduled on a specific node.

Support updating node labels, adding or deleting custom node labels for nodes with normal status.

Procedure

  1. In the left navigation pane, click Clusters > Clusters.

  2. Click the Cluster Name where the node with the label to be updated is located.

  3. On the Node tab, click the > Update Node Labels button on the right side of the node with the label to be updated.

  4. Add, modify, or delete node labels.

  5. Click Confirm.
    After the node labels are successfully updated, the number of node labels changes. You can view all label information for the node in the Node Labels item in the Node information panel.

Stop/resume scheduling node

By setting the scheduling status of a node, you can control whether newly created pods in the cluster can be scheduled on that node.

Procedure

  1. In the left navigation bar, click Clusters > Clusters.

  2. Click on the Cluster Name where the node to be stopped/resumed for scheduling is located.

  3. On the Node tab, click the on the right side of the node with the desired scheduling status, and select Stop Scheduling/Resume Scheduling.

  4. Click Confirm.

Evicting container group

Evict all container groups on a node with normal status, except for those managed by DaemonSet, to other nodes in the cluster, and set the node to an unschedulable state.

Caution: Data in locally stored container groups will be lost after eviction. Please proceed with caution.

Procedure

  1. In the left navigation bar, click Clusters > Clusters.

  2. Click on the Cluster Name where the container group to be evicted is located.

  3. On the Node tab, click on the Node Name of the container group to be evicted.

  4. Click Actions > Evict Container Group in the upper right corner.

  5. Check the information of the container group to be evicted, and click Evict.

Set taint

Set taint information for nodes with normal status.

Taint is a property of a node that can cause the node to reject or even evict a certain type of container group. Taints and tolerations on container groups work together to avoid assigning container groups to inappropriate nodes. Each node can have one or more taints applied to it, and container groups that cannot tolerate these taints will not be accepted by the node.

For example, if we find that the memory utilization of a node has reached 91%, it is not recommended to schedule new container groups on this node. We can set a taint for it. After the taint is set, Kubernetes will not schedule container groups to this node.

Learn more…

Procedure

  1. In the left navigation bar, click Clusters > Clusters.

  2. Click the Cluster Name where the node to be tainted is located.

  3. On the Node tab, click the next to the node to be tainted, and then click Set Taint.

  4. Set the key, value, and effect of the taint according to the following instructions. Multiple taints can be added to a node.

    A taint consists of key=value [effect].

    key=value is used to match the toleration of a container group. The taint indicates that the node has been tainted by key=value, and the container group scheduling is not allowed or is not preferred on this node, unless the container group can tolerate (Tolerations) the key=value taint.

    Effect is the effect of the taint, which can be one of the following:

    • NoSchedule: Indicates that scheduling is not allowed, and scheduled resources are not affected.

    • PreferNoSchedule: Indicates that scheduling is not preferred.

    • NoExecute: Indicates that scheduling is not allowed, and scheduled resources will be deleted after tolerationSeconds.

  5. Click Confirm.

Label & Taint Management

The platform supports batch setting labels and taints for nodes.

Constraints and limitations

procedure

  1. In the left navigation bar, click Cluster Management > Cluster.

  2. Click Cluster Name that expects to manage labels and taints.

  3. Under the Nodes tab, multi-select the nodes you expect to manage and click the Label and Taint Management button

    Hint: You can enter the node labels you care about in the search box on the node list page to quickly filter out the list of nodes where you expect to manage labels and taint

  4. In Batch Operate, add and fill in the operations you want to perform and click OK to submit the batch operations to the cluster.

    • Node Label: You can Add/Update the specified label for the selected node or Delete the specified label. When you select Delete, the platform will filter the list of all labels on the selected node for you, where the value of selecting Any represents deletion of all labels on the node that contains the key specified by the label.

    • Taint: You can Add/Update the specified stains for the selected node or Remove the specified stains. When you select Delete, the platform will filter the list of all labels on the selected node for you, where the value selects Any to represent the deletion of taints on all nodes that contain the key specified by the label.

    • Device Label: you can set the devices expected to be used for the selected node, where the list of devices is derived from the device plugins you have deployed in this cluster.

On/off virtualization switch

When the nodes of a self-built cluster are physical machines, you can control whether Kubernetes can schedule virtual machines (VMIs, VirtualMachineInstances) to the nodes by turning on/off the virtualization switch of the nodes.

When the switch is turned on, newly created virtual machines are allowed to be scheduled to the physical node; when the switch is turned off, newly created virtual machines are prohibited from being scheduled to the physical node, but it does not affect the virtual machines already running on the node.

Tip: For related operations and precautions, please refer to Preparing Virtualization Environment .

Delete nodes of self-built cluster

Supports deleting nodes in clusters of the type “self-built”. For example, deleting nodes that have failed in a self-built cluster.

Constraints and limitations

Procedure

  1. In the left navigation bar, click Clusters > Clusters.

  2. Click the Cluster Name of the type “self-built” where the node to be deleted is located.

  3. On the Node tab, click the > Delete on the right side of the node to be deleted.

    Tip:If you need to clean up the resources under the node after deleting the Linux node, click Download Cleanup Script at the bottom of the dialog box to download the cleanup script to the local. After the node is successfully deleted, log in to the node and execute the cleanup script.

  4. After entering the node name, click Delete.