tencent cloud

Tencent Kubernetes Engine

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
AI
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
Contact Us
Glossary

Deactivation of Scaling Group Feature

PDF
Focus Mode
Font Size
Last updated: 2024-12-13 15:46:01
To ensure a consistent user experience, TKE plans to deactivate the scaling group service on June 13, 2022. If your cluster has a created scaling group, you can convert it into a node pool through the CreateClusterNodePoolFromExistingAsg API or in the console. The conversion will not affect your business.
Through the API
Through the console
You can use the CreateClusterNodePoolFromExistingAsg API to convert the scaling group into a node pool. For detailed directions, see CreateClusterNodePoolFromExistingAsg.
1. Log in to the TKE console and click Cluster on the left sidebar.
2. On the cluster management list page, click the target cluster ID.
3. On the cluster details page, select Node Management > Scaling group.
4. On the node pool list page, select More > Create Node Pool on the right of the scaling group.
A node pool provides more stable and comprehensive elastic scaling capabilities than a scaling group, facilitating node creation, management, and termination. After the deactivation, you can use the node pool to manage created scaling groups. For more information, see Node Pool Overview.

Deactivation plan

Creation entry closure: Starting from June 6, 2022, no more scaling groups can be created in the console or through the API.
Feature deactivation and switch: The scaling group service will be deactivated on June 13, 2022. We recommend you convert your scaling group into the node pool as instructed in "Converting a scaling group into a node pool" before the deactivation date. Scaling groups that still exist after the date will be automatically converted into node pools for unified management.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback