Updating a Node Pool

Precautions

• Only clusters of v1.19 or later support the modification of the container runtime, OS, system/data disk size, data disk space allocation, and pre-/post-installation script configuration.
• Changes to the container runtime, OS, or pre-/post-installation script in a node pool apply only to new nodes. To synchronize the modification onto existing nodes, manually reset these nodes.
• After modifying node pool settings, note that some parameters take effect through different mechanisms. You can review these mechanisms when confirming the modified specifications.

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. In the right pane, click the Node Pools tab.
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	Validation
   Node Pool Name	Name of a node pool. NOTE: When the node pool name is changed, modifications to node labels will apply. This may affect workload scheduling based on node affinity. To prevent scheduling issues, update the workload scheduling settings accordingly.	None
   Enterprise Project	This parameter is available only for enterprise users who have enabled an enterprise project. After an enterprise project is selected, nodes will be created in the node pool within that project. To manage clusters and other resources like nodes, load balancers, and node security groups, you can use enterprise projects. For more details, see Enterprise Center Overview.	Changes are only automatically applied to new nodes.

   Node Configuration

   Table 2 Node configuration parameters

   Parameter	Description	Validation
   Specifications	Select node specifications that best fit your service needs. NOTE: If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes. Nodes added to a single node pool must have the same GPU or NPU type. For example, if you select the nvidia-v100 flavor, you are not allowed to select the nvidia-t4 flavor. A maximum of 20 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them. After a node pool is created, the flavors of existing nodes cannot be deleted.	Changes are only automatically applied to new nodes.
   Container Engine	CCE supports Docker or containerd as the container runtime. Available runtimes vary by cluster type, version, and OS. Select the runtime shown on the CCE console. For details, see Mapping Between Node OSs and Container Runtimes.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   OS	Select an OS type. Different types of nodes support different OSs. Public image: Select a public image for the node. Private image: Select a private image for the node. For details about how to create a private image, see Creating a Custom CCE Node Image. Shared image: You can select an image shared by other users. This option is supported by BMS and PM nodes. NOTE: Service container runtimes share the kernel and underlying calls of nodes. To ensure compatibility, select a Linux distribution version that is the same as or close to that of the final service container image for the node OS.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   Modify Login Settings	After this function is enabled, you can modify the node login mode. Password The default username is root. Enter the password for logging in to the node and confirm the password. Be sure to remember the password as you will need it when you log in to the node. Key Pair Select the key pair used to log in to the node. Private key pairs are accessible only to you. Account key pairs are shared with all users in the account. A key pair is used for identity authentication when you remotely log in to a node. If no key pair is available, click Create Key Pair. For details about how to create a key pair, see Creating a Key Pair. Image password (supported for ECSs or PMs whose OSs are private images) Retain the password of the selected image. To use this option, ensure that you have set a password for the selected image.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.

   Storage Settings

   Table 3 Configuration parameters

   Parameter	Description	Validation
   System Disk	System disk used by the node OS. The value ranges from 40 GiB to 1,024 GiB. The default value is 50 GiB. For clusters v1.28 and later, the minimum system disk size is 20 GiB. However, approximately 15 GiB is reserved for the node OS image, component installation packages (downloaded during installation and upgrades), and system component logs. Therefore, actual available space is total capacity minus reserved space. Insufficient disk space may affect node stability. Configure disk alarms to monitor remaining capacity. System Disk Encryption: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. Only the nodes of the Elastic Cloud Server (VM) type in certain regions support system disk encryption. For details, see the console. Not encrypted is selected by default. After setting System Disk Encryption to Enabled (key), choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the text box.	System disk specifications: Changes are only automatically applied to new nodes. System disk encryption: Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   System Component Storage	Select a disk for storing system components. Data Disk: added for storing container runtime and kubelet components by default. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB. This data disk cannot be detached. Otherwise, the node will be unavailable. System Disk: stores CCE resources such as downloaded images, ephemeral storage for containers, and container stdout logs. If the system disk is fully occupied, it will negatively affect the stability of the node. NOTE: In clusters v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, you can select a disk for storing system components. If CCE Node Problem Detector is used, ensure its version is 1.19.2 or later. Customizing the pod base size for a node pool will prevent you from changing System Component Storage to System Disk.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   Data Disk	A default data disk must be available for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be detached. Otherwise, the node will be unavailable. Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32,768 GiB. The default value is 100 GiB. Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. If System Component Storage is set to System Disk, you do not need to add a default data disk. In this case, all data disks are common ones. You can set the data disk size to a value ranging from 10 GiB to 32,768 GiB. The default value is 100 GiB. Advanced Settings Expand the area and configure the following parameters: Data Disk Space Allocation: allocates space for the container runtime, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see Space Allocation of a Data Disk. Enabled: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. BMS nodes do not support data disk encryption, and this option is only available in certain regions. For details, see the console. Not encrypted is selected by default. After setting Data Disk Encryption to Enabled, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the text box. Adding data disks By default, non-default data disks are created as raw disks without any processing. The number of data disks that can be attached to a node varies by node flavor. For details, see the console. You can also click Expand and select any of the following options: Default: By default, a raw disk is created without any processing. Mount Disk: The data disk is attached to a specified directory. Use as PV: applicable when there are high performance requirements on PVs. The node.kubernetes.io/local-storage-persistent label is added to the node with PV configured. The value is linear or striped. Use as ephemeral volume: applicable when there is a high performance requirement on emptyDir. PVs and EVs support the following write modes: Linear: A linear logical volume integrates one or more physical volumes. Data is written to the next physical volume when the previous one is used up. Striped: A striped logical volume stripes data into blocks of the same size and stores them in multiple physical volumes in sequence. This allows data to be concurrently read and written. A storage pool consisting of striped volumes cannot be scaled-out. This option can be selected only when there are multiple volumes. NOTE: Local PVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 2.1.23 or later. Local EVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 1.2.29 or later. Local Disk Description If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk. Local disks may break down and do not ensure data reliability. Store your service data in EVS disks, which are more reliable than local disks.	Changes are only automatically applied to new nodes.

   Network Settings

   Table 4 Configuration parameters

   Parameter	Description	Validation
   VPC	The VPC to which the cluster belongs by default, which cannot be changed.	None
   Node Subnet	The node subnet selected during cluster creation is used by default. You can choose another subnet instead. Multiple subnets: You can select multiple subnets in the same VPC for nodes. Newly added nodes will preferentially use the IP addresses from the top-ranking subnet. Single subnet: Only one subnet is configured for your node pool. If the IP addresses of a single subnet are insufficient, configure multiple subnets. Otherwise, a node pool scale-out may fail.	Changes are only automatically applied to new nodes.
   EIP	A cloud server can access the Internet only after it is bound with an EIP. To enable Internet access, bind an EIP to the server. The default value is Do not use. If you select Auto assign, configure the following parameters: EIP Type Dynamic BGP: In a network using dynamic BGP, changes can be quickly addressed by adjusting configurations via the routing protocol, ensuring stability and optimal performance. Static BGP: In a network using static BGP, changes cannot be quickly addressed, and network configurations cannot be promptly adjusted, negatively affecting user experience. Billed By Bandwidth: Dedicated bandwidth, which is billed based on bandwidth size. Traffic: Dedicated bandwidth, which is billed by traffic you have actually used. Bandwidth Size: Select the bandwidth size (in Mbit/s) based on service requirements.	Changes are only automatically applied to new nodes.

   Payment Settings

   Table 5 Payment parameters

   Parameter	Description	Validation
   Autopay	After this function is enabled, CCE will automatically process the order and charge you each time a yearly/monthly node is added to a node pool. CCE will automatically apply any applicable discounts during payment and apply charges in the specified order. For details about the deduction sequence and rules, see Enabling Auto Payment.	Changes are only automatically applied to new nodes.

   Advanced Settings

   Table 6 Advanced settings

   Parameter	Description	Validation
   Resource Tag	You can add resource tags to classify resources. You can create predefined tags on the TMS console. These tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency. For details, see Creating Predefined Tags. CCE will automatically create the CCE-Dynamic-Provisioning-Node=Node ID tag.	Changes are automatically applied to new nodes. They also apply to existing nodes if Resource tags synchronized is selected in Synchronization for Existing Nodes.
   Kubernetes Label	A key-value pair added to a Kubernetes object (such as a pod). After specifying a label, click Add for more. 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.	Changes are automatically applied to new nodes. They also apply to existing nodes if Resource tags synchronized is selected in Synchronization for Existing Nodes.
   Kubernetes Taint	This parameter is left blank by default. You can add taints to configure anti-affinity for the node. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters: Taint Key: A key must contain 1 to 63 characters, starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as a key prefix. Taint Value: A value must contain 1 to 63 characters, starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute. For details, see Managing Node Taints.	Changes are automatically applied to new nodes. They also apply to existing nodes if Resource tags synchronized is selected in Synchronization for Existing Nodes.
   Synchronization for Existing Nodes	After the options are selected, changes to resource tags and Kubernetes labels/taints in a node pool will be synchronized to existing nodes in the node pool. NOTE: When you update a node pool, pay attention to the following if you change the state of Resource tags synchronized: After the option is selected: CCE will synchronize the resource tags configured in the node pool to existing nodes. If a resource tag with the same key of a resource tag in the node pool already exists on an ECS, the value of the tag on the ECS will be changed to that of the resource tag in the node pool. Typically, it takes less than 10 minutes to synchronize resource tags onto existing nodes, depending on the number of nodes in the node pool. Issue a resource tag synchronization request only after the previous synchronization is complete. Otherwise, the resource tags may be inconsistent between existing nodes. When you update a node pool, pay attention to the following if you change the state of Kubernetes labels or Taints: When these options are deselected, the Kubernetes labels/taints of the existing and new nodes in the node pool may be inconsistent. If service scheduling relies on node labels or taints, the scheduling may fail or the node pool may fail to scale. When these options are selected: If you have modified or added labels or taints in the node pool, the modifications will be automatically synchronized to existing nodes typically in 10 minutes after Kubernetes labels or Taints is selected. If you have deleted a label or taint in the node pool, you must manually delete the label or taint on the node list page after Kubernetes labels or Taints is selected. If you have manually changed the key or effect of a taint on an existing node, a new taint will be added to the existing node after Kubernetes labels or Taints is selected. In the new taint, its key is different from the manually changed key but its value and effect are the same as those manually changed ones, or its effect is different from the manually changed effect but its key and value are the same as those manually changed ones. This is because a Kubernetes taint natively uses a key and effect as a key-value pair. The taints with different keys or effects are considered as two taints.	Changes are automatically applied to both new and existing nodes.
   New Node Scheduling	Default scheduling policy for the nodes newly added to a node pool. If you select Unschedulable, newly created nodes in the node pool will be labeled as unschedulable. In this way, you can perform some operations on the nodes before pods are scheduled to these nodes. Scheduled Scheduling: After scheduled scheduling is enabled, new nodes will be automatically scheduled after the custom time expires. Disabled: By default, scheduled scheduling is not enabled for new nodes. To manually enable this function, go to the node list. For details, see Configuring a Node Scheduling Policy in One-Click Mode. Custom: the default timeout for unschedulable nodes. The value ranges from 0 to 99 in the unit of minutes. NOTE: If auto scaling of node pools is also required, ensure the scheduled scheduling is less than 15 minutes. If a node added through Autoscaler cannot be scheduled for longer than 15 minutes, Autoscaler determines that the scale out failed and triggers another scale out. Additionally, if the node cannot be scheduled for longer than 20 minutes, the node will be scaled in by Autoscaler. After this function is enabled, nodes will be tainted with node.cloudprovider.kubernetes.io/uninitialized during a node pool creation or update.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   Pre-installation Command	Installation script command, in which CJK characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10,240. A pre-installation script runs before Kubernetes is installed. If it fails, the Kubernetes installation will also fail.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   Post-installation Command	Installation script command, in which CJK characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10,240. The script will be executed after Kubernetes software is installed, which does not affect the installation. During post-installation script execution, pods can be scheduled normally. However, if the script times out, node installation fails. To prevent pod scheduling on nodes with incomplete script execution, enable the option to schedule pods only after post-installation script completion. CAUTION: Do not use the reboot command in the post-installation script to restart the system immediately. Instead, use the shutdown -r 1 command to restart the system with a one-minute delay.	Changes are automatically applied to new nodes. For existing nodes, modifications take effect only after a reset.
   Agency	If you need to share cloud server resources with other accounts or delegate a more professional person or team to manage the resources, you can create an agency on IAM and grant the agency the permissions to manage cloud server resources. The delegated account can log in to the cloud system and switch to your account to manage resources. You do not need to share security credentials (such as passwords) with other accounts, ensuring the security of your account. If you have created an agency, choose the agency from the drop-down list. If no agency is available, click Create Agency on the right to create one. For details about agencies, see Delegating Another Account for Resource Management.	Changes are only automatically applied to new nodes.
   Custom Prefix and Suffix	The custom name prefix and suffix of a node in a node pool. After the configuration, the nodes in the node pool will be named with the configured prefix and suffix. For example, if the prefix is prefix- and the suffix is -suffix, the nodes in the node pool will be named in the format of "prefix-Node pool name with five-digit random characters-suffix". A node name consists of a maximum of 56 characters in the format of "Prefix-Node pool name with five-digit random characters-Suffix". Both prefix and suffix can contain lowercase letters, digits, periods (.), and hyphens (-). A period must be immediately preceded or followed by a lowercase letter or digit. The prefix must start with a lowercase letter; the suffix must end with a lowercase letter or digit. A node name does not support the combination of a period (.) and special characters (such as .., .-, or -.). This function is available only in clusters of v1.28.1, v1.27.3, v1.25.6, v1.23.11, v1.21.12, or later.	Changes are only automatically applied to new nodes.

4. After the configuration, click OK.

   After node pool parameters are modified, you can find the update on the Nodes page. Reset the nodes in the target node pool to synchronize the configuration update.

   

Follow-up Operations

After the settings of a node pool are updated, some settings cannot be automatically synchronized for existing nodes. You can manually synchronize the settings for these nodes. For details, see Synchronizing Node Pools.