Laman ini saat ini hanya mendukung bahasa inggris, bahasa yang telah anda telusuri sedang dipersiapkan.
关闭
Tencent Kubernetes Engine
- Release Notes and Announcements
- Release Notes
- Announcements
- Security Vulnerability Fix Description
- Release Notes
- Kubernetes Version Maintenance
- Runtime Version Maintenance Description
- Product Introduction
- Quick Start
- TKE General Cluster Guide
- Purchase a TKE General Cluster
- Permission Management
- Controlling TKE cluster-level permissions
- TKE Kubernetes Object-level Permission Control
- Cluster Management
- Images
- Worker node introduction
- Normal Node Management
- Native Node Management
- Purchasing Native Nodes
- Supernode management
- Purchasing a Super Node
- Registered Node Management
- Memory Compression Instructions
- GPU Share
- qGPU Online/Offline Hybrid Deployment
- Kubernetes Object Management
- Workload
- Configuration
- Auto Scaling
- Service Management
- Ingress Management
- CLB Type Ingress
- API Gateway Type Ingress
- Storage Management
- Use File to Store CFS
- Use Cloud Disk CBS
- Add-On Management
- CBS-CSI Description
- Network Management
- GlobalRouter Mode
- VPC-CNI Mode
- Static IP Address Mode Instructions
- Cilium-Overlay Mode
- OPS Center
- Audit Management
- Event Management
- Monitoring Management
- Log Management
- Using CRD to Configure Log Collection
- Backup Center
- TKE Serverless Cluster Guide
- Purchasing a TKE Serverless Cluster
- TKE Serverless Cluster Management
- Super Node Management
- Kubernetes Object Management
- OPS Center
- Log Collection
- Using a CRD to Configure Log Collection
- Audit Management
- Event Management
- TKE Registered Cluster Guide
- Registered Cluster Management
- Ops Guide
- TKE Insight
- TKE Scheduling
- Job Scheduling
- Native Node Dedicated Scheduler
- Cloud Native Service Guide
- Cloud Service for etcd
- Version Maintenance
- Cluster Troubleshooting
- Practical Tutorial
- Cluster
- Serverless Cluster
- Mastering Deep Learning in Serverless Cluster
- Scheduling
- Security
- Service Deployment
- Proper Use of Node Resources
- Network
- DNS
- Self-Built Nginx Ingress Practice Tutorial
- Logs
- Monitoring
- OPS
- DevOps
- Construction and Deployment of Jenkins Public Network Framework Appications based on TKE
- Auto Scaling
- KEDA
- Containerization
- Microservice
- Cost Management
- Hybrid Cloud
- Fault Handling
- Pod Status Exception and Handling
- Pod exception troubleshooter
- API Documentation
- Making API Requests
- Elastic Cluster APIs
- Resource Reserved Coupon APIs
- Cluster APIs
- Third-party Node APIs
- Network APIs
- Node APIs
- Node Pool APIs
- TKE Edge Cluster APIs
- Cloud Native Monitoring APIs
- Super Node APIs
- TKE API 2022-05-01
- Making API Requests
- Node Pool APIs
- FAQs
- TKE General Cluster
- TKE Serverless Cluster
- About OPS
- Service Agreement
- User Guide(Old)
DokumentasiTencent Kubernetes EngineTKE General Cluster GuideBackup CenterBackup and Restoration Practices
Backup and Restoration Practices
Terakhir diperbarui:2024-12-26 17:33:47
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.
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
Ya
Tidak