All Documents
Current Document

Content is empty

If you don't find the content you expect, please try another search term

Documentation

Management node labels

Last updated:2021-09-29 22:05:22

Kingsoft Cloud Container Engine (KCE) allows you to manage the labels of nodes in a cluster.

Add a label

  1. Log in to the KCE console.
  2. In the left navigation pane, click Cluster.
  3. Click the ID of the cluster in which you want to add a label to a node. The cluster details page appears.
  4. In the left navigation pane, choose Manage Nodes > Node. The Node page appears.
  5. Click Labels and Taints.
  6. Click Label. On the Label tab, select the target node and click Add Label in the Operation column or on the top of the list.
  7. In the Create Label dialog box, set the key and value and click OK. Then, the label appears in the Custom Label column.

Edit a label

  1. Log in to the KCE console.
  2. In the left navigation pane, click Cluster.
  3. Click the ID of the cluster in which you want to edit a label of a node. The cluster details page appears.
  4. In the left navigation pane, choose Manage Nodes > Node. The Node page appears.
  5. Click Labels and Taints.
  6. Click Label. On the Label tab, find the target node and click the edit icon next to the label that you want to modify.
  7. In the Edit Label dialog box, modify the value as required and click OK. Then, the updated label appears in the Custom Label column.

Remove a label

  1. Log in to the KCE console.
  2. In the left navigation pane, click Cluster.
  3. Click the ID of the cluster in which you want to remove a label from a node. The cluster details page appears.
  4. In the left navigation pane, choose Manage Nodes > Node. The Node page appears.
  5. Click Labels and Taints.
  6. Click Label. On the Label tab, find the target node and click the delete icon next to the label that you want to delete.
  7. In the Delete Label message, click OK. Then, the label disappears from the Custom Label column.

    Note

    • Make sure that the label to be deleted is not used by a service. Otherwise, the related pod may fail to be scheduled after the pod is restarted.
On this page
Pure ModeNormal Mode

Pure Mode

Click to preview the document content in full screen
Feedback