Resetting a Node

Scenario

You can reset a node to modify the node configuration, such as the node OS and login mode.

Resetting a node will reinstall the node OS and the Kubernetes software on the node. If a node is unavailable because you modify the node configuration, you can reset the node to rectify the fault.

Notes and Constraints

• To enable node resetting in CCE standard clusters, the version must be v1.13 or later.

Precautions

• Only worker nodes can be reset. If the node is still unavailable after the resetting, delete the node and create a new one.
• After a node is reset, the node OS will be reinstalled. Before resetting a node, drain the node to gracefully evict the pods running on the node to other available nodes. Perform this operation during off-peak hours.
• After a node is reset, its system disk and data disks will be cleared. Back up important data before resetting a node.
• If you reset a worker node that has an additional data disk attached on the ECS console, the attachment will be removed. To keep the data, you need to reattach the disk.
• The IP addresses of the workload pods on the node will change, but the container network access is not affected.
• There is remaining EVS disk quota.
• When a node is reset, the backend will make it unschedulable.
• Resetting a node will clear the Kubernetes labels and taints you added (those added by editing a node pool will not be lost). As a result, node-specific resources (such as local storage and workloads scheduled to this node) may be unavailable.

Resetting Nodes in the Default Pool

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Nodes. On the displayed page, click the Nodes tab.
3. In the node list of the default pool, select one or more nodes to be reset and choose More > Reset Node in the Operation column.
4. In the displayed dialog box, click Next.
5. Specify node parameters.
   Compute Settings

   Table 1 Configuration parameters

   Parameter	Description
   Specifications	Specifications cannot be modified when you reset a node.
   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. Public image: Select a public image for the node. 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

   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.
   Data Disk	At least one data disk is required for the container runtime and kubelet components. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable. Click Expand to configure Data Disk Space Allocation, which is used to allocate space for container engines, 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. 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.

   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. The predefined tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency. 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.
   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: 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 contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute. NOTICE: If taints are used, you must configure tolerations of pods. Otherwise, a scale-out may fail or pods cannot be scheduled onto the added nodes. After a node pool is created, you can click Edit to modify its configuration. The modification will be synchronized to all nodes in the node pool.
   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.
   Pre-installation Command	Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. 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	Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The script will be executed after Kubernetes software is installed, which does not affect the installation.

6. Click Next: Confirm.
7. Click Submit.