Create a node pool

This topic describes how to create a node pool in the Kingsoft Cloud Container Engine (KCE) console. To create a node pool, perform the following steps:

1. Log in to the KCE console.
2. In the left navigation pane, click Cluster.
3. Click the ID of the cluster in which you want to create a node pool. The cluster details page appears.
4. In the left navigation pane, choose Manage Nodes > Node Pool. The Node Pool page appears.

5. Click Create Node Pool. The Create Node Pool page appears.

6. Set the following parameters as required:

   • Name: the custom name of the node pool. The name must be 2 to 64 characters in length and can contain only letters, digits, and the following special characters: - , . ! $ ^ * ( ) % # & + / : ; < = > [ ] _ ` { | } ~.
   • Auto Scaling: specifies whether to enable auto scaling for the node pool. Auto scaling is disabled by default.

   • Billing Mode: the billing mode of nodes in the node pool. Valid values: Pay-By-Daily-Config and Pay-As-You-Go.

     Note

     • If auto scaling is enabled, only nodes in Pay-As-You-Go billing mode can be added to the node pool.

   • Specification items: the specifications of Kingsoft Cloud Elastic Compute (KEC) instances in the node pool, including the data center, CPU, memory, IPv6 support, architecture, instance type, image, and system disk.
   • Data Disk: specifies the size of the data disk and whether to format it or mount it to the specified directory.
   • Container Storage Directory: specifies whether to customize a directory to store container and image data. We recommend that you store container and image data in a data disk. If you do not customize a directory, container and image data is stored in the /data/docker path by default.
   • Login Mode: the login mode of the KEC instances in the node pool. Valid values: Password and Key.
   • Project: the project to which the KEC instances in the node pool belong.
   • VPC: the default VPC where the cluster resides. The VPC cannot be changed after the node pool is created.
   • Associate Subnet: the subnets where the KEC instances in the node pool reside.
   • Network Expansion Policy: the policy for selecting the subnet. Valid values:
     • Balanced Distribution: During a scale-out, the KEC instances are evenly distributed on subnets. If the target availability zone has insufficient resources for the scale-out, other subnets are selected based on the Selected First policy.
     • Selected First: During a scale-out, the KEC instances are scaled out based on the order of the subnets selected in the Associate Subnet parameter.
   • Security Group: the security group of the KEC instances in the node pool.
   • Nodes: the number of nodes in the node pool. Set this parameter based on your business requirements.
   • Node Quantity Range: the quantity range of nodes in the node pool. The number of nodes is adjusted within this range.
   • (Optional) Advanced settings:
     • Scrip To Run Before Deployment: the custom data to configure nodes. The script is run before nodes are deployed. You must ensure the reentrancy and retry logic of the script. You can view the script and its log files in the /usr/local/ksyun/kce/pre_userscript path of the node.
     • Scrip To Run After Deployment: the custom data to configure nodes. The script is run after nodes are deployed. You must ensure the reentrancy and retry logic of the script. You can view the script and its log files in the /usr/local/ksyun/kce/userscript path of the node.
     • Cordon: specifies whether to cordon worker nodes. After you cordon worker nodes, no more pods can be scheduled onto the worker nodes. To schedule new pods onto the worker nodes, uncordon the worker nodes. For more information, see Cordon or drain a node.
     • Label: the label to be attached to the nodes in the node pool. Labels allow you to implement flexible scheduling. You can customize labels based on your business requirements.
     • Taints: the taints to be attached to the nodes in the node pool. For more information, see Manage node taints.
7. Click Create. After the node pool is created, it appears on the Node Pool page.