All Documents
Current Document
Content is empty
If you don't find the content you expect, please try another search term
Content is empty
If you don't find the content you expect, please try another search term
Last updated：2021-11-11 17:43:14
The node pool feature enables you to efficiently and conveniently manage nodes in Kubernetes clusters. For example, you can create and destroy nodes, manage nodes by group, enable and disable auto scaling for nodes, and modify node pool configurations. In addition, the node pool feature supports auto scaling. When pods in a cluster fail to be scheduled due to insufficient resources, a scale-out is triggered. When a specific proportion of node resources are idle, a scale-in is triggered.
Note
- The node pool feature is available, which inherits all features of scaling groups. If scaling groups exist in your cluster but you cannot perform operations on them, we recommend that you click OK in the Upgrade Scaling Group to Node Pool dialog box on the Scaling Group page to upgrade scaling groups to node pools.
A node pool can contain one or more nodes. You can create node pools of different sizes and types in your cluster to manage the nodes by group. Each node pool has unique configurations. You can modify node pool information and node template configuration for each node pool.
| Feature | Description | Instruction |
|---|---|---|
| Create node pools | Allows you to create node pools. | Only nodes in Pay-By-Daily-Config or Pay-As-You-Go billing mode can be added to a node pool. |
| Enable and disable auto scaling | Allows you to enable or disable auto scaling. · If auto scaling is enabled, the number of nodes in the node pool is automatically adjusted based on the workloads in the cluster. · If auto scaling is disabled, you must manually adjust the number of nodes in the node pool. |
You can disable auto scaling after it is enabled. However, after that, you cannot enable auto scaling again. |
| Adjust the number of nodes | Allows you to adjust the number of nodes in a node pool. | If auto scaling is enabled, the number of nodes in the node pool is automatically adjusted based on the workloads in the cluster. In this case, you cannot manually adjust it. · If you manually decrease the number of nodes in the node pool, the system first removes the nodes created in scale-outs and then the existing nodes added to the node pool. Nodes that are manually added to the cluster are only removed but not deleted during a scale-in. To delete these nodes, you must go to the Kingsoft Cloud Elastic Compute (KEC) console. |
| Modify node pool information | Allows you to modify the node pool name, number of nodes, node quantity range, labels, and taints, and disable auto scaling. | In the Modify Node Pool Information dialog box, you can also select Updates on labels and taints apply to all existing nodes in the node pool as required. · If you select this option, the updates on labels and taints take effect on the existing and newly added nodes in the node pool, which may cause the rescheduling of pods on the existing nodes. Exercise caution when you perform this operation. · If you do not select this option, the update on labels and taints takes effect only on newly added nodes. |
| Modify node template configuration | Allows you to modify the node configuration, node type, operating system, system disk, data disk, data disk mount, container storage directory, network expansion policy, security group, scripts to run before and after deployment, and cordon settings of a node pool, and change the associated subnet for a node pool. | The update on node template configuration takes effect only on newly added nodes. |
| Manage node pools | Allows you to manage and modify the node pool information and node template configuration of a node pool in a centralized manner. | None. |
| Delete node pools | Allows you to delete existing node pools. When you delete a node pool, you can choose whether to delete the nodes in the node pool. | If you choose to delete the nodes in the node pool, the data on the system disk and data disk of the node pool is deleted and cannot be recovered. Exercise caution when you perform this operation. |
| Add existing nodes to a node pool | Allows you to add existing nodes in the cluster to a node pool. Make sure that the nodes have not been added to other node pools and observe the following requirements: · The nodes and node pool belong to the same subnet. · Only nodes in the Normal state can be added to the node pool. · Only nodes in Pay-By-Daily-Config or Pay-As-You-Go billing mode can be added to the node pool. |
This operation is not supported for node pools with auto scaling enabled. |
| Remove nodes from a node pool | Allows you to remove nodes from a node pool and choose whether to delete them at the same time. | This operation is not supported for node pools with auto scaling enabled. |
Note
- You can enable auto scaling for a node pool only when you create it. After auto scaling is enabled, the number of nodes in the node pool is automatically adjusted based on the workloads in the cluster. You cannot manually adjust the number of nodes, add existing nodes to a node pool, or remove nodes from a node pool. When you modify node pool configuration of a node pool, you can disable auto scaling. After that, you cannot enable auto scaling again. For more information, see Configure automatic cluster scaling.
- Configure node pools in the Kingsoft Cloud Container Engine (KCE) console instead of the Auto Scaling console. Otherwise, some features of node pools may fail.
Log in to the KCE console to manage node pools as required. For more information about the operations, see the following topics:
Pure Mode
