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

Cluster Deletion

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-03-19 18:30:12
Cloud Service for etcd clusters do not support cascade deletion. Before you delete a cluster, make sure that all stored data in the cluster has been removed. Cluster deletion cannot be restored. Operate with caution.
Note:
Before you delete a cluster, it is recommended that you check the instance monitoring data to confirm if client businesses are still using the cluster.
For clusters with password authentication enabled, you cannot check the data storage status. Therefore, they are not subject to the cascade deletion restriction. Operate with caution.

Directions

Clearing the Stored Data

To clear all key-value data in an etcd cluster, you can use the etcdctl command-line tool to perform the following operations:
1. Ensure that etcdctl is installed. If not, download and install the latest version from the GitHub release page of etcd.
2. Set environment variables for etcdctl, typically including ETCDCTL_API, ETCDCTL_ENDPOINTS, ETCDCTL_CACERT, ETCDCTL_CERT, and ETCDCTL_KEY.
3. Before you delete the data, you are suggested to use the etcdctl tool to create a snapshot of the etcd cluster and save it as a file for backup and recovery. Execute the following command:
etcdctl --command-timeout=30s snapshot save $etcdID-final.db
--command-timeout=30s is an optional parameter that sets the command timeout to 30 seconds. If the command is not executed successfully within this time, it will be terminated.
snapshot save $etcdID-final.db is the actually executed command. It creates a snapshot of the etcd cluster and saves it as a file. $etcdID is a variable. You need to replace it with the actual etcd node ID or any other name you want to use.
4. Use etcdctl to delete all key-value data. The following command will delete all key-value pairs under the root directory:
etcdctl del "" --prefix

Deleting the Cluster

2. Choose More > Terminate/Return on the right of the cluster on the Cloud native etcd page, as shown in the figure below:

3. Select other cloud resources to be terminated on the Terminate/return instances page.
Snapshot data stored in the COS bucket will be retained by default. If the option of COS snapshot data deletion is selected, the snapshot data of the cluster in the bucket will be deleted, but the bucket will be retained.
CLB resources generated after public network access is enabled will be deleted along with the Cloud Service for etcd cluster.
4. Click Confirm.



Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan