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, you need to 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 and 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	Modify the number of nodes based on service requirements.
   Auto Scaling	By default, this parameter is disabled. After you enable autoscaler by clicking , nodes in the node pool are automatically created or deleted based on service requirements. Maximum Nodes and Minimum Nodes: You can set the maximum and minimum number of nodes to ensure that the number of nodes to be scaled is within a proper range. Priority: A larger value indicates a higher priority. For example, if this parameter is set to 1 and 4 respectively for node pools A and B, B has a higher priority than A, and auto scaling is first triggered for B. If the priorities of multiple node pools are set to the same value, for example, 2, the node pools are not prioritized and the system performs scaling based on the minimum resource waste principle. After the priority is updated, the configuration takes effect within 1 minute. Cooldown Period: Enter a period, in minutes. This field indicates the period during which the nodes added in the current node pool cannot be scaled in. If the Autoscaler field is set to on, install the autoscaler add-on to use the autoscaler feature.

   Advanced Settings

   Table 2 Advanced settings

   Parameter	Description
   Kubernetes Label	Click Add Label to set the key-value pair attached to the Kubernetes objects (such as pods). 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 in Tag Management Service (TMS). Predefined tags are visible to all service resources that support the tagging function. You can use these tags to improve tagging 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 when a node is added. For existing nodes, you need to manually reset the nodes for the modification to take effect.
   Taint	This field is left blank by default. You can add taints to set anti-affinity for the node. A maximum of 10 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 inventory 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 when a node is added. For existing nodes, you need to manually reset the nodes for the key pair to take effect.

4. When the configuration is complete, 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.