- Product Updates
- Product Introduction
- Purchase Guide
- Quick Start
- User Guide
- Notes on the New Console
- High-risk Operations of Container Service
- Deploying Containerized Applications in the Cloud
- Kubernetes API Operation Guide
- Open Source Components
- Cluster Management
- Cluster Overview
- Cluster Hosting Modes Introduction
- Image explanation of TKE-Optimized series
- Cluster Lifecycle
- Creating a Cluster
- Deleting a Cluster
- Cluster Scaling
- Connecting to a Cluster
- Upgrading a Cluster
- Enabling IPVS for a Cluster
- GlobalRouter VPC-CNI Mode Description
- Enabling GPU Scheduling for a Cluster
- CVM Container Cluster Network
- Registered Container Cluster in Cloud Networking
- Configuring Intra-Region and Cross-region Peering
- Setting Communication Between Cluster Container and IDC
- Custom Kubernetes Component Launch Parameters
- Node Management
- Node Pool Management
- Kubernetes Object Management
- Overview
- Namespace
- Workload
- Deployment Management
- StatefulSet Management
- DaemonSet Management
- Job Management
- CronJob Management
- Setting the Resource Limit of Workload
- Setting the Scheduling Rule for a Workload
- Setting the Health Check for a Workload
- Setting the Run Command and Parameter for a Workload
- Using a Container Image in a TCR Enterprise Instance to Create a Workload
- Managing StatefulSets with Static Pod IP Addresses
- Auto Scaling
- Configuration
- Service Management
- Ingress Management
- Storage Management
- Helm Application
- Image Registries
- Application Market
- OPS Center
- Remote Terminals
- Elastic Cluster Guide
- Edge Cluster Guide
- Best Practices
- Permission Management
- Overview
- Description of Role Permissions Related to Service Authorization
- TKE Image Registry Resource-level Permission Settings
- Controlling TKE cluster-level permissions
- TKE Kubernetes Object-level Permission Control
- Fault Handling
- API documentation
- History
- Introduction
- API Category
- Making API Requests
- Other APIs
- Node-related APIs
- Cluster APIs
- AcquireClusterAdminRole
- CreateClusterEndpoint
- CreateClusterEndpointVip
- DeleteCluster
- DeleteClusterEndpoint
- DeleteClusterEndpointVip
- CreateCluster
- DescribeClusterEndpointStatus
- DescribeClusterKubeconfig
- DescribeClusterEndpointVipStatus
- DescribeClusterInstances
- DescribeClusterSecurity
- ModifyClusterAttribute
- DescribeClusters
- ModifyClusterEndpointSP
- DeleteClusterInstances
- AddExistedInstances
- API Mapping Guide
- Scaling group APIs
- Data Types
- Error Codes
- FAQs
- Notice
- Service Level Agreement
- Glossary
- User Guide(Old)
- Product Updates
- Product Introduction
- Purchase Guide
- Quick Start
- User Guide
- Notes on the New Console
- High-risk Operations of Container Service
- Deploying Containerized Applications in the Cloud
- Kubernetes API Operation Guide
- Open Source Components
- Cluster Management
- Cluster Overview
- Cluster Hosting Modes Introduction
- Image explanation of TKE-Optimized series
- Cluster Lifecycle
- Creating a Cluster
- Deleting a Cluster
- Cluster Scaling
- Connecting to a Cluster
- Upgrading a Cluster
- Enabling IPVS for a Cluster
- GlobalRouter VPC-CNI Mode Description
- Enabling GPU Scheduling for a Cluster
- CVM Container Cluster Network
- Registered Container Cluster in Cloud Networking
- Configuring Intra-Region and Cross-region Peering
- Setting Communication Between Cluster Container and IDC
- Custom Kubernetes Component Launch Parameters
- Node Management
- Node Pool Management
- Kubernetes Object Management
- Overview
- Namespace
- Workload
- Deployment Management
- StatefulSet Management
- DaemonSet Management
- Job Management
- CronJob Management
- Setting the Resource Limit of Workload
- Setting the Scheduling Rule for a Workload
- Setting the Health Check for a Workload
- Setting the Run Command and Parameter for a Workload
- Using a Container Image in a TCR Enterprise Instance to Create a Workload
- Managing StatefulSets with Static Pod IP Addresses
- Auto Scaling
- Configuration
- Service Management
- Ingress Management
- Storage Management
- Helm Application
- Image Registries
- Application Market
- OPS Center
- Remote Terminals
- Elastic Cluster Guide
- Edge Cluster Guide
- Best Practices
- Permission Management
- Overview
- Description of Role Permissions Related to Service Authorization
- TKE Image Registry Resource-level Permission Settings
- Controlling TKE cluster-level permissions
- TKE Kubernetes Object-level Permission Control
- Fault Handling
- API documentation
- History
- Introduction
- API Category
- Making API Requests
- Other APIs
- Node-related APIs
- Cluster APIs
- AcquireClusterAdminRole
- CreateClusterEndpoint
- CreateClusterEndpointVip
- DeleteCluster
- DeleteClusterEndpoint
- DeleteClusterEndpointVip
- CreateCluster
- DescribeClusterEndpointStatus
- DescribeClusterKubeconfig
- DescribeClusterEndpointVipStatus
- DescribeClusterInstances
- DescribeClusterSecurity
- ModifyClusterAttribute
- DescribeClusters
- ModifyClusterEndpointSP
- DeleteClusterInstances
- AddExistedInstances
- API Mapping Guide
- Scaling group APIs
- Data Types
- Error Codes
- FAQs
- Notice
- Service Level Agreement
- Glossary
- User Guide(Old)
Introduction
The node pool feature is currently in beta. To join the beta test, please submit a ticket.
To help you better manage nodes in a Kubernetes cluster, TKE introduced the concept of a node pool. Basic node pool features allow you to conveniently and quickly create, manage, and terminate nodes and dynamically scale nodes in and out.
- When a Pod in the cluster cannot be scheduled due to insufficient resources, scale-out will be triggered automatically, reducing labor costs.
- When a scale-in condition is met, such as when a node is idle, scale-in will be triggered automatically, reducing resource costs.
The following figure shows the overall architecture of a node pool.
Generally, all nodes in a node pool share the following attributes:
- Node operating system
- Launch parameters of Kubernetes components for nodes
- Custom launch script for nodes
- Kubernetes Label and Taints settings for nodes
In addition, TKE extends the following attributes for a node pool:
- Node pool-level operating system
- Maximum number of Pods for each node in a specific node pool
Use Cases
When you need to use a large-scale cluster, we recommend that you use a node pool to manage nodes to improve the usability of the large-scale cluster. The following table describes multiple use cases for managing large-scale clusters and shows the effect of node pools in each use case.
| Use Case | Effect |
|---|---|
| A cluster includes many heterogeneous nodes with different model configurations. | A node pool allows you to manage the nodes by groups in a unified manner. |
| A cluster needs to frequently scale nodes in and out. | A node pool reduces operating costs. |
| The scheduling rules for applications in a cluster are complex. | Node pool labels allow you to quickly specify service scheduling rules. |
| Routine maintenance is required for nodes in a cluster. | A node pool allows you to conveniently upgrade the Kubernetes version and the Docker version. |
Features and Notes
| Feature | Description | Notes |
|---|---|---|
| Create | Add a node pool | We recommend that you do not create more than 20 node pools for a single cluster. |
| Delete |
|
When you delete a node pool, if you select to terminate nodes, the nodes will not be retained. You can create new nodes later if required. |
| Enable auto scaling | When auto scaling is enabled for a node pool, the number of nodes in the node pool is automatically adjusted according to the workload of the cluster. | Do not enable or disable auto scaling in the Scaling Group console. |
| Disable auto scaling | When auto scaling is disabled for a node pool, the number of nodes in the node pool is not automatically adjusted according to the workload of the cluster. | |
| Adjust node pool size | You can directly adjust the number of nodes in a node pool. If you decrease the number of nodes, a random node in a scaling group will be removed. | It’s not recommended to manually adjust the size of a node pool when auto scaling is enabled. |
| Adjust node pool configurations | You can modify the node pool name, the number range of nodes in a scaling group, and the Kubernetes Label and Taints attributes for nodes in the node pool. | Modifications of the Label and Taints attributes take effect for all the nodes in a node pool and may cause Pods to be rescheduled. |
| Add an existing node | You can add a non-clustered Pod to a node pool if the following requirements are met:
|
In normal cases, we recommend that you directly create a node pool instead of adding an existing node to a node pool. |
| Remove a node | You can remove a manually added node from a node pool and retain the t in the cluster. Nodes cannot be directly removed from a scaling group. | We recommend that you add or remove nodes in a node pool by adjusting the size of the node pool. |
| Convert a scaling group into a node pool |
|
This operation is irreversible. Be sure you understand the features of node pools before conversion. |
Relevant Operations
You can log in to the Tencent Kubernetes Engine console and perform node pool-related operations according to the following documents:
Was this page helpful?