This document describes how to create a node pool in a cluster via the TKE console and describes node pool-related operations, such as viewing, managing, and deleting a node pool.
TKE allows you to convert an existing scaling group in a cluster to a node pool. If a scaling group has already been created in the cluster, you can create a node pool by using the existing scaling group.
After the node pool is created, you can view the related information of the node pool. For more information, see Viewing a Node Pool. The original Scaling group cannot be viewed again.
On the “Cluster Management” page, click the desired cluster ID to open the “Deployment” page.
In the left sidebar, choose Node Management -> Node pool to open the “Node pool list” page.
Click Create Node Pool to open the “Create Node Pool” page. Specify the configurations according to the following descriptions.
Node pool name: you can customize the name of the node pool based on service requirements to facilitate subsequent resource management.
Billing Mode: valid values include Pay-as-you-go and Spot. You can select the value as required. For more information, see Payment Modes.
Supported network: the system provides IP addresses within the address range of the node network for servers in the cluster.
This configuration item is specified at the cluster level and therefore cannot be modified after configuration.
Model Settings: click Select the model. On the “Model Settings” page, select the values as required according to the following descriptions:
Availability Zone: launch configurations do not contain availability zone information. This option is only used to filter available instance types in the availability zone.
Model: you can select the model by specifying the number of CPU cores, memory size, and instance type. For more information, see Instance Types.
System disk: controls the storage and schedules the operating of Cloud Virtual Machines (CVMs). You can view the system disk types available for the selected model and select the system disk as required. For more information, see Cloud Disk Types.
Data disk: stores all the user data. You can specify the values according to the following descriptions. Each model corresponds to different data disk settings. For more information, see the following table:
|Model||Data Disk Settings|
|Standard, Memory Optimized, Computing, and GPU||No option is selected by default. If you select any of these options, you must specify the cloud disk settings and formatting settings.|
|High I/O and Big Data||These options are selected by default and cannot be cleared. You can customize the formatting settings for the default local disks.|
|Batch-based||This option is selected by default, but can be cleared. If this option is selected, you can purchase only default local disks. You can customize the formatting settings for the default local disks.|
Add Data Disk (Optional): click Add Data Disk and specify the settings according to the preceding table.
Public Bandwidth: Assign free public IP is selected by default. The system assigns a free public IP address. You can select Bill By Traffic or Bill by Bandwidth for the billing mode as required and customize the network speed. For more information, see Public Network Billing.
Login Methods: you can select any one of the following login methods as required:
Security Groups: the default value is the security group specified when the cluster is created. You can replace the security group or add a security group as required.
Quantity: the desired capacity. You can specify this value as required.
If auto scaling has been enabled for the node pool, this quantity will be automatically adjusted according to the loads of the cluster.
Node Quantity Range: the number of nodes will be automatically adjusted within the specified node quantity range and will not exceed the specified range.
Supported subnets: select an available subnet as required.
(Optional) Click More Settings to view or configure more information, as shown in the following figure.
Tolerations. You can specify this parameter for all the nodes of the node pool so that Pods that do not meet the relevant conditions cannot be scheduled to these nodes and will be drained from these nodes.
Assume that Taints is set to
The value of Taints usually consists of
effect. Valid values of
- PreferNoSchedule: optional condition. A Pod is not likely to be scheduled to a node with a taint that cannot be tolerated by the Pod.
- NoSchedule: when a node contains a taint, a Pod without the corresponding toleration to the taint will never be scheduled to the node.
- NoExecute: when a node contains a taint, a Pod without the corresponding toleration to the taint will not be scheduled to the node and any such Pods already on the node will be drained.
key1=value1:PreferNoSchedule. The following figure shows the configurations in the TKE console:
/usr/local/qcloud/tke/userscriptpath of the node.
Click Create Node Pool to create the node pool.
After a node pool is created, you can manage the node pool according to the following documents: