Creating a Node

Prerequisites

• At least one cluster is available.
• A key pair is available for remote node login using key-pair authentication. For details, see Creating a Key Pair.

  If you use a password for login, skip this step.

Notes and Constraints

• The DNS configuration of a subnet where a node is located cannot be modified because OBS and other dependent services are necessary for creating nodes.
• When IPv4/IPv6 dual stack is enabled, DHCP unlimited lease cannot be enabled for the selected node subnet.

Precautions

• To maintain node stability, a specific number of CCE node resources will be reserved for Kubernetes components like kubelet, kube-proxy, and Docker, based on the node specifications. Therefore, the total number of node resources and the number of allocatable node resources for your cluster are different. The larger the node specifications, the more the containers deployed on the node. Therefore, more node resources need to be reserved to run Kubernetes components. For details, see Node Resource Reservation Rules.
• Networks including VM networks and container networks of nodes are all managed by CCE. Do not add or delete network interfaces, or change routes and IP addresses. Otherwise, services may be unavailable. For example, the network interface named gw_11cbf51a@eth0 on the node is the container network gateway and is not modifiable.
• Pay-per-use nodes in a cluster will be deleted directly after you perform certain operations on the Nodes page of the CCE console, while yearly/monthly nodes cannot be deleted directly on the CCE console. Instead, you can click Billing in the upper right corner, choose Orders > Unsubscriptions and Returns/Exchanges, and unsubscribe from the corresponding resources.

Procedure

After a cluster is created, you can create nodes for the cluster.

1. Log in to the CCE console.
2. In the navigation pane of the CCE console, choose Clusters. Click the target cluster name to access its details page.
3. In the navigation pane, choose Nodes. On the page displayed, click the Nodes tab and then Create Node in the upper right corner. Configure node parameters.

   Node Configuration

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

   Table 1 Node configuration parameters

   Parameter	Description
   Billing Mode	The following billing modes are supported: 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 by month or by year. Pay-per-use Resources will be billed based on usage duration. You can provision or delete resources at any time. Spot price A postpaid billing mode, in which a spot cloud server will be billed based on the service duration at a lower price than that of a pay-per-use ECS cloud server with the same specifications. For details, see Spot Pricing ECSs. NOTE: If you purchase a data disk and an EIP while creating a spot pricing ECS, they will be automatically released when the ECS is released. If you attach data disks or bind EIPs to an existing spot pricing ECS, these resources must be manually released after the ECS is deleted. Spot pricing ECSs cannot be reset, accepted for management, removed, migrated, changed to yearly/monthly, or upgraded by resetting the cluster. Before resetting a cluster for an upgrade, delete spot pricing nodes and set the number of pods in the spot pricing node pool to 0. Spot pricing ECSs may be released if the quoted price is lower than the market price or if there are not enough resources available. Install the latest CCE Node Problem Detector add-on in the cluster so that you can receive a notification 5 minutes before a spot pricing ECS is released. This add-on generates a ReceivedReclaimNodeNotification event, adds taint node-problem-controller.cce.io/SpotPriceNodeReclaimNotification: NoExecute to the node (spot pricing ECS), and evicts pods on the node. This allows pods to be migrated to other nodes before the spot pricing ECS is deleted.
   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. Select Random to deploy your node in a random AZ based on the selected node flavor. 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	Select a node type based on service requirements. Then, the available node flavors will be automatically displayed in the Specifications area for you to select. CCE standard clusters support the following node types: ECS (VM): A VM ECS is used as a cluster node. ECS (PM): A QingTian-backed bare metal server is used as a cluster node. BMS: A traditional bare metal server is used as a cluster node. Local disks of bare metal servers can be used as data disks. CCE Turbo clusters support the following node types: ECS (VM): A VM ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple network interfaces. Select a server type displayed on the CCE console. ECS (PM): A QingTian-backed bare metal server is used as a cluster node.
   Specifications	Select node flavors as needed. A node needs at least 2 CPU cores and 4 GiB of memory. The available node flavors vary depending on AZs. Obtain the flavors displayed on the console. NOTE: Kunpeng (Arm) nodes can be added to CCE clusters. The specifications displayed on the node creation can be used.
   Container Runtime (Original 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.
   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.
   Node Name	Name of the node. 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. Enter 1 to 56 characters. It must start with a lowercase letter and not end with a hyphen (-) or period (.). Only lowercase letters, digits, periods (.), and hyphens (-) are allowed. Periods (.) must be immediately preceded and followed by lowercase letters or digits.
   Enterprise Project	This parameter is available only for enterprise users who have enabled an enterprise project, and the cluster version must be v1.21.15-r0, v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. After an enterprise project is selected, nodes will be created in it. 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.
   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.

   Storage Settings

   Configure storage resources on a node for the containers running on it. Select a disk type and configure its size based on service requirements. For details about EVS disks, see Disk Types and Performance.

   Table 2 Configuration parameters

   Parameter	Description
   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. NOTE: General Purpose SSD V2 disks allow you to specify the disk IOPS and throughput. For details, see EVS performance data. General Purpose SSD V2 EVS disks are available only in clusters v1.21.15-r0, v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions. 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. System disk encryption is supported only on VM-type ECSs and is available only in certain regions. For details, see the console. Not encrypted is selected by default. If you select Enable (key name) for System Disk Encryption, 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. If you select Enable (key ID) for System Disk Encryption, enter a KMS key (which can be shared by others) in the current region.
   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 32,768 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 and later, you can select the storage location of system components. If the CCE Node Problem Detector add-on is required in the cluster, install v1.19.2 or a later version. For details about this add-on, see CCE Node Problem Detector.
   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. NOTE: 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. General Purpose SSD V2 disks allow you to specify the disk IOPS and throughput. For details, see EVS performance data. General Purpose SSD V2 EVS disks are available only in clusters v1.21.15-r0, v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions. Advanced Settings For the default data disk used by the container runtime and kubelet, expand advanced settings 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. Write Mode: You can select Linear or Striped for the default data disk. Data Disk Encryption: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. Data disk encryption is unavailable for BMS nodes. It is offered only in certain regions. For details, see the console. Not encrypted is selected by default. If you select Enable (key name) for Data Disk Encryption, 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. If you select Enable (key ID) for Data Disk Encryption, enter a KMS key (which can be shared by others) in the current region. 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: Select this option 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. NOTE: Local PVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is v2.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 v1.2.29 or later. If the data disk is not mounted by default, the following write modes are supported: 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 is available only if there are at least two data disks.

   Network Settings

   Configure networking resources to allow node and containerized application access.

   Table 3 Configuration parameters

   Parameter	Description
   VPC/Node Subnet	The node subnet selected during cluster creation is used by default. You can choose another subnet instead.
   Node IP	IP address of the specified node. By default, the value is randomly allocated.
   EIP	An ECS without a bound EIP cannot access the Internet or be accessed from public networks. The default value is Do not use. Use existing and Auto assign are supported. 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.

   Advanced Settings

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

   Table 4 Advanced configuration parameters

   Parameter	Description
   Resource Tag	You can add resource tags to classify resources. A maximum of eight resource tags can be added. 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 automatically creates the CCE-Cluster-ID=<cluster-ID> and CCE-Dynamic-Provisioning-Node=<node-ID> tags.
   Kubernetes Label	A key-value pair attached to 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.
   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. NOTE: For a cluster 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 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 Create Cloud Server Group to create one. After the ECS group is created, click the refresh icon.
   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.
   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.
   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.
   Kubernetes Node Name	The Kubernetes node name is the value of metadata.labels.kubernetes.io/hostname in the YAML file of the node. The following two values are supported: Node private IP: The value must be the same as the private IP address of the node (default value). Cloud server name: Use the custom cloud server name configured in node settings. Cloud server names may be duplicate. To prevent naming conflicts, CCE adds a random five-digit suffix to each cloud server name. NOTICE: This function is available only when the cluster version is v1.23.4-r0 or later. The name of a cloud server can be specified as the name of a Kubernetes node only when the cloud server is created or managed. After the cloud server is created or managed, the Kubernetes node name cannot be changed. For details, see ECS Names, Node Names, and Kubernetes Node Names. Existing nodes in the cluster retain their private IP addresses as Kubernetes node names. Newly created or added nodes use cloud server names instead. This inconsistency between node names and private IP addresses may require adaptation. For example, when configuring node affinity, you cannot use the kubernetes.io/hostname:<node-private-IP-address> label to target specific nodes. To change the Kubernetes node name of the existing nodes to the cloud server name, remove these nodes from the cluster and accept them again. Before doing so, learn about the possible impacts on services when removing or accepting a node.

4. After completing the preceding settings, specify the number of nodes to be purchased and click Next: Confirm review the configuration, pricing, and specifications.
5. Read the instructions, select the check box, and click Submit to start node creation.

   If the node will be billed on a yearly/monthly basis, click Pay Now and follow on-screen prompts to pay the order.

6. Click Back to Node List. The node has been created when its status changes to Running. Wait for the creation to complete.

ECS Names, Node Names, and Kubernetes Node Names

• ECS name: the name of an ECS on the ECS page. You can customize an ECS name when creating the ECS (node).
• Node name: the name of a node on the CCE console, which can be synchronized with the ECS name on the ECS console. However, after the Kubernetes node name is specified, the change of the ECS name cannot be synchronized to the node name.
• Kubernetes node name: the value of metadata.labels.kubernetes.io/hostname in the YAML file of the node. The name of a cloud server can be specified as the name of a Kubernetes node only when the cloud server is created or managed. After the cloud server is created or managed, the Kubernetes node name cannot be changed.

Figure 1 shows the synchronization relationship between ECS names, node names, and Kubernetes node names.

Figure 1 Relationship between node names

Helpful Links

• CCE needs to reserve certain node resources for the kubelet component and system processes. For details, see Node Resource Reservation Rules.
• To configure the data disk space of a node based on service requirements, see Space Allocation of a Data Disk.
• The maximum number of pods supported by each node varies based on parameter settings. For details, see Maximum Number of Pods That Can Be Created on a Node.
• To automatically execute scripts for custom settings when creating a node, see Executing the Pre- or Post-installation Script During Node Creation.
• To remove a node from a node pool, do not delete the node directly. Instead, adjust the number of nodes in the node pool. For details, see Scaling a Node Pool.
• To perform batch operations on nodes with the same configurations, use the function of Creating a Node Pool to quickly create, manage, or destroy nodes. Additionally, enabling node scaling can automatically scale in and out node resources, improving resource utilization.
• If an exception occurs during node creation, locate the fault by referring to How Do I Troubleshoot Problems Occurred When Adding Nodes to a CCE Cluster?