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)
DocumentationTencent Kubernetes EngineCloud Native Service GuideCloud Service for etcdVersion MaintenanceVersion Maintenance Mechanism
Version Maintenance Mechanism
Last updated: 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.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No