Accepting Nodes for Management

Scenario

In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs or BMSs) to your cluster for management. These nodes can be billed on a yearly/monthly or pay-per-use basis.

• When accepting an ECS, you can reset its OS to a standard public image offered by CCE. If you choose to do so, you must reconfigure the password or key, as the previous one will become invalid.
• During the acceptance process, LVM information, including volume groups (VGs), logical volumes (LVs), and physical volumes (PVs), will be deleted from the system disks and data disks attached to the selected ECSs. Ensure this information has been backed up.
• During the acceptance of an ECS, do not perform any operation on the ECS through the ECS console.

Notes and Constraints

• BMSs and ECSs, as well as DeHs can be managed.

Prerequisites

The cloud servers to be managed must meet the following requirements:

• The node to be accepted must be Running or Stopped, must not be used by other clusters, and must not have the CCE-Dynamic-Provisioning-Node label.
• The node to be accepted and the cluster must be in the same VPC. (If the cluster version is earlier than v1.13.10, the node to be accepted and the CCE cluster must be in the same subnet.)
• Data disks must be attached to the nodes to be managed if the system components of these nodes are stored separately. These nodes can be attached with either a local disk (disk-intensive disk) or a data disk of at least 20 GiB. Additionally, any data disks already attached must not be smaller than 10 GiB. For details about how to attach a data disk, see Adding a Disk to an ECS.
• The node to be accepted must have at least 2 CPU cores, 4 GiB of memory, and only one network interface.
• Only cloud servers with the same data disk configuration can be accepted in batches for management.
• For IPv6-enabled clusters, only nodes with IPv6 enabled in the cluster's subnet can be accepted.
• CCE Turbo clusters require that each node supports supplementary network interfaces, or you will need to bind at least 16 network interfaces. For details about the node flavors, see the options provided on the console when you create a node.
• Data disks that have been partitioned will be ignored during node management. Ensure that there is at least one unpartitioned data disk meeting the specifications attached to the node.

Procedure

1. Log in to the CCE console and go to the cluster where the node to be accepted resides.
2. In the navigation pane, choose Nodes. On the displayed page, click the Nodes tab and then Accept Node in the upper right corner.
3. Specify node parameters.

   Node Configuration

   Table 1 Node configuration parameters

   Parameter	Description
   Node Pool	Default node pool: You can add nodes that meet the management requirements to the default node pool of the cluster. Custom node pool: You only need to select the nodes that meet the management requirements. These nodes will use the basic, network, and advanced settings of the custom node pool. You do not need to configure other parameters. For details, see Accepting Nodes in a Node Pool.
   Specifications	Click Select Cloud Server and select the servers to be accepted. Multiple cloud servers can be selected for batch acceptance, but only those with identical data disk configurations can be added together. If a cloud server contains multiple data disks, select one of them for the container runtime and kubelet.
   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.
   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.

   Table 2 Configuration parameters

   Parameter	Description
   System Disk	Directly use the system disk of the cloud server.
   Default Data Disk	Select a data disk for the container runtime and kubelet.
   System Component Storage	Select a disk for storing system components. Data Disk: A default data disk must be added for the container runtime and kubelet. 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.
   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. This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0. If System Component Storage is set to System Disk, you do not need to add a default data disk. All data disks are general-purpose ones. This function is available for clusters v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions. Click Expand to configure Data Disk Space Allocation. This reserves space for the container runtime, images, and ephemeral storage to ensure normal operation. For details about how to allocate data disk space, see Space Allocation of a Data Disk. For other data disks, a raw disk is created without any processing by default. You can also click Expand and select Mount Disk to mount the data disk to a specified directory. Data disks can also be used as local PVs or local EVs.

   Advanced Settings

   Table 3 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 will automatically create the CCE-Dynamic-Provisioning-Node=Node ID tag.
   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.
   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. NOTE: If taints are used, you must configure pod tolerations. Otherwise, scale-out operations may fail, or pods may fail to schedule onto the added nodes.
   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.
   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.

4. Click Next: Confirm, review the usage note, select the check box, and click Submit.