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.
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. |
Expected Initial Nodes |
Number of nodes to be created in this node pool. A maximum of 50 nodes that can be created at a time. |
Configurations
Parameter |
Description |
|---|---|
Node Type |
Select a node type based on service requirements. Then, you can select a proper flavor from the node flavor list. CCE standard clusters support the following node types:
CCE Turbo clusters support the following node types:
|
Specifications |
Select a node flavor based on service requirements. The available node flavors vary depending on regions or AZs. For details, see the CCE console.
NOTE:
|
Container Engine |
The container engines supported by CCE include Docker and containerd, which may vary depending on cluster types, cluster versions, and OSs. Select a container engine based on the information displayed on the CCE console. For details, see Mapping between Node OSs and Container Engines. |
OS |
Select an OS type. Different types of nodes support different OSs.
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. |
Login Mode |
|
Storage Settings
Parameter |
Description |
|---|---|
System Disk |
System disk used by the node OS. The value ranges from 40 GiB to 1024 GiB. The default value is 50 GiB. 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.
|
Data Disk |
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.
NOTE:
Advanced Settings Expand the area and configure the following parameters:
Adding data disks A maximum of 16 data disks can be attached to an ECS and 10 to a BMS. By default, a raw disk is created without any processing. You can also click Expand and select any of the following options:
NOTE:
Local PVs and local EVs can be written in the following modes:
|
Network Settings
Parameter |
Description |
|---|---|
Virtual Private Cloud |
The VPC to which the cluster belongs by default, which cannot be changed. |
Node Subnet |
The node subnet selected during cluster creation is used by default. You can choose another subnet instead.
|
Node IP Address |
Random allocation is supported. |
Associate Security Group |
Security group used by the nodes created in the node pool. A maximum of five security groups can be selected. When a cluster is created, a node security group named {Cluster name}-cce-node-{Random ID} is created and used by default. Traffic needs to pass through certain ports in the node security group to ensure node communications. Ensure that you have enabled these ports if you select another security group. NOTE:
After a node pool is created, its associated security group cannot be modified. |
Advanced Settings
Parameter |
Description |
|---|---|
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. |
Kubernetes Label |
A key-value pair added to a Kubernetes object (such as a pod). After specifying a label, click Add Label for more. A maximum of 20 labels can be added. Labels can be used to distinguish nodes. With workload affinity settings, pods can be scheduled to a specified node. For more information, see Labels and Selectors. |
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:
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. |
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. |
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.
NOTE:
|
Max. Pods |
Maximum number of pods that can run on the node, including the default system pods. 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 icon. |
Pre-installation Command |
Pre-installation script command, in which Chinese 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 10240. The script will be executed before Kubernetes software is installed. Note that if the script is incorrect, Kubernetes software may fail to be installed. |
Post-installation Command |
Pre-installation script command, in which Chinese 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 10240. The script will be executed after Kubernetes software is installed, which does not affect the installation. NOTE:
Do not run the reboot command in the post-installation script to restart the system immediately. To restart the system, run the shutdown -r 1 command to restart with a delay of one minute. |
Agency |
An agency is created by the account administrator on the IAM console. Using 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. |
User-defined node name prefix and suffix |
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". NOTICE:
|