Scenario

This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.

Notes and Constraints

• The autoscaler add-on needs to be installed for node auto scaling. For details about the add-on installation and parameter configuration, see autoscaler.
• Auto scaling is available only for pay-per-use node pools, not for those billed by year or month.

Procedure

The new console supports yearly/monthly-billed nodes in a node pool.

1. Log in to the CCE console.
2. Click the cluster name to open its details page, choose Nodes on the left, and click the Node Pools tab on the right.
3. In the upper right corner of the page, click Create Node Pool.

   Basic Settings

   Table 1 Basic settings

   Parameter	Description
   Node Pool Name	Name of a node pool. By default, the name is in the format of Cluster name-nodepool-Random number. If you do not want to use the default name format, you can customize the name.
   Nodes	Number of nodes to be created in this node pool.
   Auto Scaling	By default, auto scaling is disabled. After you enable auto scaling by switching on , nodes in the node pool will be automatically created or deleted based on cluster loads. 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: Set this parameter based on service requirements. 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. 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. NOTE: CCE selects a node pool for auto scaling based on the following policies: CCE uses algorithms to determine whether a node pool meets the conditions to allow scheduling of a pod in pending state, including whether the node resources are greater than requested by the pod, and whether the nodeSelect, nodeAffinity, and taints meet the conditions. In addition, the node pools that fail to be scaled (due to insufficient resources or other reasons) and are still in the 15-minute cool-down interval are filtered. If multiple node pools meet the scaling requirements, the system checks the priority of each node pool and selects the node pool with the highest priority for scaling. The value ranges from 0 to 100 and the default priority is 0. The value 100 indicates the highest priority, and the value 0 indicates the lowest priority. If multiple node pools have the same priority or no priority is configured for them, the system selects the node pool that will consume the least resources based on the configured VM specification. If the VM specifications of multiple node pools are the same but the node pools are deployed in different AZs, the system randomly selects a node pool to trigger scaling. Scale-In Cooling Interval: Set this parameter in the unit of minute or hour. This field indicates the period during which the nodes added in the current node pool cannot be scaled in. Scale-in cooling intervals can be configured in the node pool settings and the autoscaler add-on settings. Scale-in cooling interval configured in a node pool This interval indicates the period during which nodes added to the current node pool after a scale-out operation cannot be deleted. This interval takes effect at the node pool level. Scale-in cooling interval configured in the autoscaler add-on The interval after a scale-out indicates the period during which the entire cluster cannot be scaled in after the autoscaler add-on triggers scale-out (due to the unschedulable pods, metrics, and scaling policies). This interval takes effect at the cluster level. The interval after a node is deleted indicates the period during which the cluster cannot be scaled in after the autoscaler add-on triggers scale-in. This interval takes effect at the cluster level. The interval after a failed scale-in indicates the period during which the cluster cannot be scaled in after the autoscaler add-on triggers scale-in. This interval takes effect at the cluster level. NOTE: You are advised not to store important data on nodes in a node pool because after auto scaling, data cannot be restored as nodes may be deleted. If the Autoscaler field is set to on, install the autoscaler add-on to use the autoscaler feature.

   Compute Settings

   You can configure the specifications and OS of a cloud server, on which your containerized applications run.

   Table 2 Configuration parameters

   Parameter	Description
   Billing Mode	Two options are available: Yearly/Monthly You must specify the required duration if Yearly/Monthly is selected. You can choose whether to select Auto-renew based on site requirements. Your order will automatically renew on a monthly or yearly basis, depending on if you purchased 1-9 months, or 1-3 years. Pay-per-use
   AZ	AZ where the node is located. Nodes in a cluster can be created in different AZs for higher reliability. The value cannot be changed after the node is created. You are advised to select Random to deploy your node in a random AZ based on the selected node flavor. NOTE: In a CCE Turbo cluster, an AZ is randomly selected from available AZs, and all nodes will be created in the selected AZ. An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. To enhance workload availability, create nodes in different AZs.
   Node Type	For a CCE cluster, ECS and BMS are supported.
   Container Runtime	Container runtime used on the node. Different container runtimes support different node specifications and cannot be changed after the node is created. runC: The runC runtime is used. Kata: The Kata runtime is used. If you select this type for both nodes and workloads, the workloads run only on the nodes that use the Kata runtime. For details about common containers and secure containers, see Secure Containers and Common Containers.
   Container Engine	For a CCE cluster, only Docker is supported.
   Specifications	Select node specifications that best fit your business needs.
   OS	Select an OS type. Different types of nodes support different OSs. For details, see Mapping between Node OSs and Container Engines. Public image: Select an OS for the node. Private image: You can use private images for bare-metal servers (BMSs). For details about how to create a private image, see Using a Private Image to Build a Worker Node Image (OBT).
   Node Name	Name of the node, which must be unique. When nodes (ECSs) are created in batches, the value of this parameter is used as the name prefix for each ECS. The system generates a default name for you, which can be modified. A node name must start with a lowercase letter and cannot end with a hyphen (-). Only digits, lowercase letters, and hyphens (-) are allowed.
   Login Mode	You can use a password or key pair to log in to nodes. If Login Mode is set to 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. You can select a shared key. 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 on how to create a key pair, see Creating a Key Pair.

   Storage Settings

   Configure storage resources on a node for the containers running on it. Set the disk size according to site requirements.

   Table 3 Configuration parameters

   Parameter	Description
   System Disk	System disk used by the node OS. The value ranges from 40 GB to 1,024 GB. The default value is 50 GB.
   Data Disk	Data disk used by the container runtime and kubelet on the node. The value ranges from 100 GB to 32,768 GB. The default value is 100 GB. At least one data disk is required for the container runtime and kubelet. The data disk cannot be deleted or uninstalled. Otherwise, the node will be unavailable. Click Expand to set the following parameters: Allocate Disk Space: Select this option to define the disk space occupied by the container runtime to store the working directories, container image data, and image metadata. For details about how to allocate data disk space, see Data Disk Space Allocation. Encryption: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption function. Encryption is not selected by default. After you select Encryption, you can select an existing key in the displayed dialog box. If no key is available, click View Key List to create a key. After the key is created, click the refresh icon. Adding Multiple Data Disks A maximum of four data disks can be added. By default, raw disks are created without any processing. 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. 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. It is recommended that you store service data in EVS disks, which are more reliable than local disks.

   Network Settings

   Configure networking resources to allow node and containerized application access.

   Table 4 Configuration parameters

   Parameter	Description
   Node Subnet	The node subnet selected during cluster creation is used by default. You can choose another subnet instead.

   Advanced Settings

   Configure advanced node capabilities such as labels, taints, and startup command.

   Table 5 Advanced configuration parameters

   Parameter	Description
   Kubernetes Label	Click Add to set the key-value pair attached to the Kubernetes objects (such as pods). A maximum of 19 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.
   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. For details, see Creating Predefined Tags. CCE will automatically create the "CCE-Dynamic-Provisioning-Node=node id" tag.
   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: For a cluster of v1.19 or earlier, the workload may have been scheduled to a node before the taint is added. To avoid such a situation, select a cluster of v1.19 or later.
   Max. Pods	Maximum number of pods that can run on the node, including the default system pods. Value range: 16 to 256 This limit prevents the node from being overloaded with pods. This number is also decided by other factors. For details, see Maximum Number of Pods That Can Be Created on a Node.
   ECS Group	An ECS group logically groups ECSs. The ECSs in the same ECS group comply with the same policy associated with the ECS group. Anti-affinity: ECSs in an ECS group are deployed on different physical hosts to improve service reliability. Select an existing ECS group, or click Add ECS Group to create one. After the ECS group is created, click the refresh button.
   Pre-installation Command	Enter commands. A maximum of 1,000 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. It is commonly used to format data disks.
   Post-installation Command	Enter commands. A maximum of 1,000 characters are allowed. The script will be executed after Kubernetes software is installed and will not affect the installation. It is commonly used to modify Docker parameters.
   Agency	An agency is created by the account administrator on the IAM console. By creating an agency, you can share your cloud server resources with another account, or entrust a more professional person or team to manage your resources. If no agency is available, click Create Agency on the right to create one.

4. Click Next: Confirm.
5. Click Submit.