Updating a Node Pool

Constraints

• When editing the resource tags of the node pool. The modified configuration takes effect only for new nodes. To synchronize the configuration to the existing nodes, manually reset the existing nodes.
• Updates of kubernetes labels and taints are automatically synchronized to existing nodes. You do not need to reset nodes.

Updating a Node Pool

1. Log in to the CCE console.
2. Click the cluster name to access the cluster console. Choose Nodes in the navigation pane and click the Node Pools tab on the right.
3. Click Update next to the name of the node pool you will edit. Configure the parameters in the displayed Update Node Pool page.
   Basic Settings

   Table 1 Basic settings

   Parameter	Description
   Node Pool Name	Name of the node pool.
   Nodes	Change the number of nodes based on service requirements.

   Advanced Settings

   Table 2 Advanced settings

   Parameter	Description
   Kubernetes Label	A Kubernetes label is a key-value pair added to a Kubernetes object (such as a pod). After specifying a label, click Add. A maximum of 20 labels can be added. Labels can be used to distinguish nodes. With workload affinity settings, container pods can be scheduled to a specified node. For more information, see Labels and Selectors. NOTE: After a Kubernetes label is modified, the inventory nodes in the node pool are updated synchronously.
   Resource Tag	You can add resource tags to classify resources. You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. CCE will automatically create the "CCE-Dynamic-Provisioning-Node=node id" tag. NOTE: After a resource tag is modified, the modification automatically takes effect on newly added nodes. For existing nodes, manually reset the nodes for the modification to take effect.
   Taint	This field is left blank by default. You can add taints to configure node anti-affinity. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters: Key: A key must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key. Value: A value must start with a letter or digit and can contain a maximum of 63 characters, including letters, digits, hyphens (-), underscores (_), and periods (.). Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute. For details, see Managing Node Taints. NOTE: After a taint is modified, the existing nodes in the node pool are updated synchronously.
   Edit key pair	Only node pools that use key pairs for login support key pair editing. You can select another key pair. NOTE: The edited key pair automatically takes effect on newly added nodes. For existing nodes, manually reset the nodes for the modification to take effect.
   Pre-installation Command	Enter commands. A maximum of 1000 characters are allowed. The script will be executed before Kubernetes software is installed. Note that if the script is incorrect, Kubernetes software may fail to be installed. NOTE: The modified pre-installation command automatically takes effect on newly added nodes. For existing nodes, manually reset the nodes for the modification to take effect.
   Post-installation Command	Enter commands. A maximum of 1000 characters are allowed. The script will be executed after Kubernetes software is installed and will not affect the installation. NOTE: The modified post-installation command automatically takes effect on newly added nodes. For existing nodes, manually reset the nodes for the modification to take effect.

4. After the configuration, click OK.

   After the node pool parameters are updated, go to the Nodes page to check whether the node to which the node pool belongs is updated. You can reset the node to synchronize the configuration updates for the node pool.