Release Notes and Announcements

Release Notes

Announcements

Release Notes

Product Introduction

Overview

Strengths

Architecture

Scenarios

Features

Concepts

Native Kubernetes Terms

Common High-Risk Operations

Regions and Availability Zones

Service Regions and Service Providers

Open Source Components

Purchase Guide

Purchase Instructions

Purchase a TKE General Cluster

Purchasing Native Nodes

Purchasing a Super Node

Getting Started

Beginner’s Guide

Quickly Creating a Standard Cluster

Examples

Container Application Deployment Check List

Cluster Configuration

General Cluster Overview

Cluster Management

Network Management

Storage Management

Node Management

GPU Resource Management

Remote Terminals

Application Configuration

Workload Management

Service and Configuration Management

Component and Application Management

Auto Scaling

Container Login Methods

Observability Configuration

Ops Observability

Cost Insights and Optimization

Scheduler Configuration

Scheduling Component Overview

Resource Utilization Optimization Scheduling

Business Priority Assurance Scheduling

QoS Awareness Scheduling

Security and Stability

TKE Security Group Settings

Identity Authentication and Authorization

Application Security

Multi-cluster Management

Planned Upgrade

Backup Center

Cloud Native Service Guide

Cloud Service for etcd

TMP

TKE Serverless Cluster Guide

TKE Registered Cluster Guide

Use Cases

Cluster

Serverless Cluster

Scheduling

Security

Service Deployment

Network

Release

Logs

Monitoring

OPS

Terraform

DevOps

Auto Scaling

Containerization

Microservice

Cost Management

Hybrid Cloud

Troubleshooting

Disk Full

High Workload

Memory Fragmentation

Cluster DNS Troubleshooting

Cluster kube-proxy Troubleshooting

Cluster API Server Inaccessibility Troubleshooting

Service and Ingress Inaccessibility Troubleshooting

Common Service & Ingress Errors and Solutions

Engel Ingres appears in Connechtin Reverside

CLB Ingress Creation Error

Troubleshooting for Pod Network Inaccessibility

Pod Status Exception and Handling

Authorizing Tencent Cloud OPS Team for Troubleshooting

CLB Loopback

API Documentation

History

Introduction

API Category

Making API Requests

Elastic Cluster APIs

Resource Reserved Coupon APIs

Cluster APIs

Third-party Node APIs

Relevant APIs for Addon

Network APIs

Node APIs

Node Pool APIs

TKE Edge Cluster APIs

Cloud Native Monitoring APIs

Scaling group APIs

Super Node APIs

Other APIs

Data Types

Error Codes

TKE API 2022-05-01

FAQs

TKE General Cluster

TKE Serverless Cluster

About OPS

Hidden Danger Handling

About Services

Image Repositories

About Remote Terminals

Event FAQs

Resource Management

Service Agreement

TKE Service Level Agreement

TKE Serverless Service Level Agreement

Glossary

Node Pool FAQs

PDF

Modo Foco

Tamanho da Fonte

Última atualização: 2024-12-23 15:16:18

This document ‍lists the common questions and issues during the usage of general node pools.
What is the relationship between a node pool and a scaling group?
A node pool is a collection of nodes with similar specifications, configurations, and attributes. You can manage the nodes in batch through the TKE console, such as configuring node specifications, labels, taints, scripts and other parameters. You can create node pools with different billing modes (such as pay-as-you-go, spot) in a cluster. The underlying implementation of a node pool relies on Auto Scaling. There are two main concepts:
A scaling group contains a collection of CVM instances that follow the same policies and are used for the same scenario. Attributes of a scaling group include the maximum and minimum numbers of CVM instances and more.
Launch configuration is the template for automatic creation of CVMs. It specifies the CVM instance type, system disk/data disk types and capacities, key pair, security group, etc.
Each node pool corresponds to a scaling group, and each scaling group corresponds to a launch configuration. You can check the bound launch configuration and scaling group in  the node pool details page in the TKE console.
Which node pool parameters can I modified?
Reminder:
To ensure the proper scaling of node pools, DO NOT modify parameters in the AS console unless they are stated in this document.
Parameter
How to modify
Node pool name
TKE console > Node pool information
﻿
Auto Scaling
﻿
Node range
﻿
Cloud tag, Deletion protection
﻿
Labels, Taints
TKE console > Node pool information: You can specify whether to apply the modifications to existing nodes.
Operating system
TKE console > Node configuration details: The modifications only apply to nodes newly added to the node pool.
Runtime components
﻿
Secondary models
TKE console > Node configuration details
A node pool can contain up to 10 models (including the primary model).
The list shows only instance types available in the AZ of the node pool subnet.
If a GPU-model taken as the primary model, , the driver is specified upon node pool creation. The secondary model must also be a GPU model.
Custom data
TKE console > Node configuration details: Modifications only apply to nodes newly added to the node pool.
Note:
DO NOT directly modify the custom data in the launch configuration of AS, which may cause the failure of adding nodes to the cluster.
Security group
AS console > Launch configuration details:. The modifications only apply to nodes newly added to the node pool.
Instance name (node name)
AS console > Launch configuration > Advanced: The modifications only apply to nodes newly added to the node pool.
Subnet
AS console > Scaling group details: Modifications only apply to nodes newly added to the node pool.
Instance creation policy/Retry policy
AS console > Scaling groups > Policy information: Modifications take effect from the next auto scaling task.
Which node pool parameters should not be modified
Parameter
Description
Billing mode
You cannot modify the billing mode in the TKE console. In addition, we suggest NOT** to modify the instance billing mode of a launch configuration in the AS console.
Data disk
The data disk cannot be modified. In addition, it is recommended not to modify the capacity of data disks, and not to add or delete a data disk in the launch configuration of AS. Otherwise, the pending Pods may fail to be scheduled to the newly added nodes.
Supported network (VPC)
The VPC cannot be modified. In addition, it is recommended not to modify the supported network on the scaling group details page of AS, otherwise it may cause the failure of node expansion.
Note:
Each node pool corresponds to a unique scaling group and launch configuration. The launch configuration cannot be bound to other scaling groups, otherwise the node pool may fail to be deleted.
It is recommended not to modify other parameters of the scaling group in the AS console
﻿

Ajuda e Suporte

Esta página foi útil?

Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.

comentários

tencent cloud

Tencent Kubernetes Engine

Node Pool FAQs

What is the relationship between a node pool and a scaling group?

Which node pool parameters can I modified?

Which node pool parameters should not be modified

Ajuda e Suporte

Parameter	How to modify
Node pool name	TKE console > Node pool information
Auto Scaling
Node range
Cloud tag, Deletion protection
Labels, Taints	TKE console > Node pool information: You can specify whether to apply the modifications to existing nodes.
Operating system	TKE console > Node configuration details: The modifications only apply to nodes newly added to the node pool.
Runtime components
Secondary models	TKE console > Node configuration details A node pool can contain up to 10 models (including the primary model). The list shows only instance types available in the AZ of the node pool subnet. If a GPU-model taken as the primary model, , the driver is specified upon node pool creation. The secondary model must also be a GPU model.
Custom data	TKE console > Node configuration details: Modifications only apply to nodes newly added to the node pool. Note: DO NOT directly modify the custom data in the launch configuration of AS, which may cause the failure of adding nodes to the cluster.
Security group	AS console > Launch configuration details:. The modifications only apply to nodes newly added to the node pool.
Instance name (node name)	AS console > Launch configuration > Advanced: The modifications only apply to nodes newly added to the node pool.
Subnet	AS console > Scaling group details: Modifications only apply to nodes newly added to the node pool.
Instance creation policy/Retry policy	AS console > Scaling groups > Policy information: Modifications take effect from the next auto scaling task.

Parameter	Description
Billing mode	You cannot modify the billing mode in the TKE console. In addition, we suggest NOT** to modify the instance billing mode of a launch configuration in the AS console.
Data disk	The data disk cannot be modified. In addition, it is recommended not to modify the capacity of data disks, and not to add or delete a data disk in the launch configuration of AS. Otherwise, the pending Pods may fail to be scheduled to the newly added nodes.
Supported network (VPC)	The VPC cannot be modified. In addition, it is recommended not to modify the supported network on the scaling group details page of AS, otherwise it may cause the failure of node expansion.