Add Node
The maximum number of Node nodes for a single cluster is 5000, and up to 50 Node nodes can be added at once on the console page.
**Click sequentially: Details→Cluster→Node→Add Node
| Configuration Item | Description |
|---|---|
| Subnet | Set the subnet where the initial node and Pod are located. Nodes in the cluster can be in different subnets under the same VPC. |
| Type | Node type, supports UHost cloud server (including GPU cloud server), PHost physical cloud server and bare metal server. |
| Availability Zone | Master/Node’s availability zone. In regions with multiple availability zones, you can choose multi-availability zone UK8S cluster. It is recommended to distribute the Master nodes in multiple availability zones when creating the cluster. |
| Node Image | Set the UHost image of the cluster node, you can choose a custom image, but it must be based on the UK8S standard image production. For details, please refer to Create Custom Image If you want to use a GPU node, please refer to Image Description in GPU Node. CPU machine image can choose from: Centos 7.6, Ubuntu 20.04, Anolis 8.6 images. |
| Node Specifications | Including machine type, CPU platform, CPU, memory, system disk type, data disk type, data disk size, etc. The configuration of different types of models is detailed in the corresponding cloud product documentation |
| Hardware Isolation Group | Master nodes are by default in the same hardware isolation group, the hardware isolation group can strictly ensure that each cloud server within the group falls on different physical machines. Each isolation group can add up to 7 cloud servers in a single availability zone. For details, see Hardware Isolation Group |
| Maximum Pod Count | The maximum number of Pods that a single Node node can support |
| Label | Node node label, see Kubernetes official documentation: Labels and Selectors |
| Taint | Node node taint, see Kubernetes official documentation: Taints and Tolerations |
| Disable Nodes | Enable the option to disable nodes, and the node will join the cluster as a non-schedulable node, which can be enabled as needed. |
| Custom Data | Refers to the configuration script that the system automatically runs when the host starts for the first time or each time. This script can be passed into the metadata server by console API and other means, and obtained by the cloud-init program inside the host. The script follows the standard CloudInit syntax. This script will block the UK8S install script, i.e., the install of K8S related components such as Kublet, Scheduler, etc. will only start after this script is executed. |
| Initial Script | This script is only executed once after UK8S starts, and it is executed after the K8S related components are installed successfully. It follows the standard shell syntax, and the execution result will be stored in the /var/log/message/ directory. |