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

Version Maintenance Mechanism

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-03-19 18:30:11
This document introduces the versions supported by Cloud Service for etcd of Tencent Cloud and etcd of the community edition. This can help you choose the version that can best meet your business needs when using Cloud Service for etcd.

Version Definition

Major version: etcd versions are in the format of x.y.z. x indicates the major version, y indicates the minor version, and z indicates the patch version. They follow the requirements of Semantic Versioning. For example, the current versions are 3.5.4 and 3.4.13.
Minor version: The tke.x suffix indicates the minor version corresponding to the current major version. For example, the current version is v3.4.13-tke.5.
Note:
If a version has no suffix, it is an open-source version in the community.

Version Maintenance Strategy

Cluster Creation

The platform supports creating clusters of the latest 2 major versions of etcd, such as 3.5.4 and 3.4.13. When a new version is released and it supports upgrades, the earlier version no longer supports cluster creation. For example, if the version 3.6.x is released and it supports upgrade from 3.5.4 to 3.6.x, 3.4.13 will no longer support cluster creation. If version 3.6.x is released but does not support upgrades, 3.4.13 still supports cluster creation.
Note:
Only the latest minor versions of the current major versions can be selected for cluster creation.

Upgrade and Ops Guarantee

The platform focuses on guaranteeing the normal upgrade and stable operation of the latest two major versions of etcd. For example, if the current latest version is 3.5.4, the platform focuses on guaranteeing the upgrade feature of versions 3.5.4 and 3.4.13, meanwhile supports troubleshooting, fault recovery, and bug fixing. Clusters of outdated versions may face the risks of unstable operation and upgrade failures. Please upgrade the version in time.
Note:
Cluster upgrades include major version upgrades and minor version upgrades.

Ticket Submission

Cloud Service for etcd provides technical support for the latest 2 major versions of etcd, including Q&A, online guidance, troubleshooting, and problem solving. However, for clusters with outdated versions, Cloud Service for etcd does not guarantee the quality and effectiveness of provided technical support.

Suggestions on etcd Major Version Selection

This document provides version selection suggestions from the perspectives such as stability, performance, and usability.
Stability: 3.4 series versions have undergone large-scale usage and verification by global users for 2-3 years, and the overall stability is better than that of 3.5 series versions. The 3.5.4 and later versions fixed the critical bugs in earlier 3.5 versions. The open-source project Kubernetes has also used 3.5.4 in its version 1.25, and the stability in core scenarios has met the production environment requirements.
Performance: Version 3.5.4 has merged a series of performance optimization PRs, significantly reduced the cluster startup time, and improved read/write QPS.
Usability: 3.5 series versions have solved the dependency management problems in 3.4 series versions and earlier versions through package modularization, which reduces burden for the developers. The use of 3.5 series versions is good for subsequent version upgrades.
In summary, version 3.5.4 is recommended for creating clusters. For migrating existing clusters, you can choose the version same as the source clusters.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan