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
DocumentationTencent Kubernetes EngineRelease Notes and AnnouncementsAnnouncementsVersion Upgrade of Master Add-On of TKE Managed Cluster

Version Upgrade of Master Add-On of TKE Managed Cluster

PDF
Focus Mode
Font Size
Last updated: 2023-05-18 10:40:07

Upgrade time

TKE plans to upgrade the minor Kubernetes version of the master add-on of the TKE managed cluster in batches from 10:00 PM to 5:00 AM on October 12–13, 17–18, and 24–27, 2022.

Upgrade scope

This upgrade involves the master add-on of managed clusters, with the major Kubernetes version between v1.16 and v1.22. After the upgrade, the master add-on will be on the latest minor version of the current major version. For example, if the current master add-on of your cluster is on v1.20.6-tke.15, and the latest version launched by TKE is v1.20.6-tke.27, the upgraded version will be v1.20.6-tke.27.

Upgrade content

This upgrade contains:
1. Performance enhancement: Optimize the kube-apiserver list performance of large clusters and improve etcd storage stability.
2. Security enhancement: Combine the fix PR of the key community vulnerability CVE-2022-3172.
3. Stability enhancement: Combine the fix PR of multiple community features and improves kubelet, kube-scheduler, and HPA capabilities.
4. Feature support: Support dedicated schedulers for native nodes, in-place Pod configuration adjustment, and super node creation.

Upgrade description

The minor version of the master add-on is fully compatible with earlier versions, and you don't need to reset the Kubernetes add-on startup parameters, as the original settings (if any) will be retained. This upgrade won't change the major Kubernetes version of the master add-on, nor the Kubernetes version of the node. For more information on TKE Kubernetes version revisions, see TKE Kubernetes Revision Version History. If you have any questions, contact us.
Note
Kubernetes on v1.14 or earlier will no longer be iterated, and no more technical support is available. We recommend you upgrade your cluster as soon as possible. For detailed directions, see Upgrading a Cluster.




Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback