Release Notes and Announcements
- Release Notes
- Announcements
- Release Notes
Product Introduction
Purchase Guide
- Purchase Instructions
- Purchase a TKE General Cluster
- Purchasing Native Nodes
- Purchasing a Super Node
Getting Started
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
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

Backup and Restoration Practices

Modo Foco

Tamanho da Fonte

Última atualização: 2025-09-29 10:56:53

Overview
This document describes how to perform backup and restoration operations with accidental deletion of the service-controller resource in a cluster as an example.
Directions
1. Enabling Periodic Backup
1. Log in to the TKE console and select Cluster in the left sidebar.
2. Install the tke-backup add-on in cluster add-on management and ensure that the add-on status is displayed as Success. For detailed installation steps, see Installing an Add-On on the Add-On Management Page.
﻿
3. On the Backup Center > Backup Repository page, click Create to create a backup repository and complete the repository configuration. For operation details, see Creating a Backup Repository.
﻿
4. On the Backup Management page, create a periodic backup for the cluster. For operation details, see Creating a Backup.
﻿
5. In the backup list, confirm whether the status is normal.
2. Simulating Accidental Deletion
Simulate accidental deletion of the service-controller resource object under the kube-system namespace of a cluster. At this time, an exception occurs when a service object is added to the cluster.
﻿
3. Completing the Restoration Process
1. On the Backup Center > Restoration Management page, select a cluster and create a restoration task under it. For operation details, see Creating a Restoration Task.
Since service-controller is deployed under the kube-system namespace, we select the corresponding namespace for restoration.
For conflict management, we select Do not overwrite. It indicates that except for service-controller, other identically named resource objects running under the kube-system namespace will not be updated by backup data in this restoration.
﻿
2. On the Backup Center > Restoration Management page, confirm the execution status of the restoration task.
3. In the background, check whether the corresponding Pod of service-controller is running normally and whether the business has been restored.
﻿