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

Deleting Native Nodes

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-06-27 11:09:15
This document describes how to delete native nodes from node pools.

Note

Native nodes support declarative management. If you delete nodes while not modifying the required number of nodes in a node pool, new nodes are created immediately after you delete nodes.
Native nodes are managed in node pools and cannot be managed directly in clusters.
Deleting a native node releases all the resources on the node and does not support restoration. We recommend that you proceed with caution.

Directions

Pay-as-you-go node pool

1. Log in to the TKE console and select Cluster in the left sidebar.
2. On the cluster list page, click the ID of the target cluster to go to the details page.
3. Select Node Management > Worker Node > Node Pool in the left sidebar , and click the node pool ID in the node pool list to enter the node pool details page.
4. In the node list, select the target node and then click Delete . In the pop-up window, check Adjust the expected number of instances (If checked, it means that after deleting the current node, the node pool quantity will be reduced by 1. Otherwise the node pool will maintain the current expected instance number through continuous expansion).

5. Click Confirm to complete the node deletion.
Note:
For the pay-as-you-go node pool, when no specific nodes are designated for deletion and you choose to reduce the number of nodes directly by clicking Adjust quantity, the system will randomly delete redundant node replicas.

Monthly Subscription Type

1. Log in to the TKE console, and select Clusters in the left sidebar.
2. On the cluster list page, click the ID of the target cluster to go to the details page.
3. Select Node Management > Worker Node > Node Pool in the left sidebar , and click the node pool ID in the node pool list to enter the node pool details page.
4. In the node list, click Adjust quantity , to reduce the number of nodes in the pop-up window. In the subsequent confirmation window and refund window, separately click Confirm to complete the deletion of monthly subscription nodes. For example, if the current node pool has 5 native monthly subscription nodes and you wish to delete 2 specific nodes, first adjust the quantity to 3, and then select 2 monthly subscription nodes from the current node list for deletion.
5. In the node list, you can also select a monthly subscription node or a batch of nodes to be deleted, and then click Delete .
Note:
Since monthly subscription nodes involve refund processes, they cannot be deleted randomly like pay-as-you-go nodes. You must confirm the pop-up window information before deletion.
Refunds for monthly subscription nodes before expiration will be calculated according to the pay-as-you-go price. Proceed with caution.

Handling of Resources Associated with Nodes

Machines and system disks: After the native node is deleted, the machine and system disk resources will be completely terminated and cannot be restored. Proceed with caution.
EIP: If your node was configured with public network bandwidth at the time of creation, the bound EIP will be terminated along with the deletion of the node and cannot be restored. Proceed with caution.
Data disk: If your node was bound to a data disk at the time of creation, it will be terminated along with the deletion of the node and cannot be restored. It is recommended to back up your data in advance before deletion.

Ajuda e Suporte

Esta página foi útil?

comentários