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

Data Synchronization

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-03-19 18:30:12

Overview

This document describes data synchronization from the source etcd cluster to a Cloud Service for etcd cluster in the console for unified management.

Prerequisites

etcd clusters have been created.

Directions

2. Go to the etcd cluster list page, select the region at the top of the page, and click the name of the target etcd cluster in the cluster list below.
3. Go to the Data synchronization page and click Create synchronization task, as shown in the figure below:

4. Select the task type.
Type 1: Automatically import all data from the source etcd cluster to the target cluster at one time by using a snapshot.
Type 2: Synchronize data from the source etcd cluster to the target cluster in real time. (This type is not available currently.)
5. Click Next to configure the task, as shown in the figure below:

5.1 Fill in the service address of the source etcd cluster. For an existing Cloud Service for etcd cluster, you can obtain the access address of the cluster from the Basic information page.
5.2 Complete the key or certificate information based on the authentication method of the source etcd cluster. For an existing Cloud Service for etcd cluster, you can obtain the certificate information on the cluster from the Basic information page, select TLS authentication, and fill in the certificate information, as shown in the figure below:
Note:
A normal network connection is required between the source etcd cluster and the target cluster, which means that they should be deployed in the same VPC. Otherwise, you are suggested to use the snapshot management feature to synchronize data.

6. Click Next to check the configuration. After the task configuration is completed, the backend will conduct a connection test based on the access address and authentication information of the source etcd cluster. The test covers network connection, permission settings, version support, and data volume.
7. Click Confirm to start synchronization. The synchronization between the source etcd cluster and the target cluster is expected to take about 5 minutes.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan