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
DokumentasiTencent Kubernetes EngineRelease Notes and AnnouncementsAnnouncementsHost Operation System Release for Super Node Pods (Mitigated NodeLost Issue)

Host Operation System Release for Super Node Pods (Mitigated NodeLost Issue)

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-02-11 15:42:18
To enrich the features, Tencent Kubernetes Engine (TKE) plans to release a new host OS version for super nodes on March 10, 2025 (UTC+8). The incremental pods on super nodes will gradually use the new OS version.

Time

The operating system will gradually apply to the incremental pods starting from March 10, 2025 (UTC+8).

Impact Scope

This change will apply to the pods that are rebuilt or newly added on super nodes in TKE Standard Cluster and TKE Serverless Cluster. The pods currently running on super nodes will not be affected.

About the New Version of Host OS

The new version of the host OS is based on Tencent's commercial TencentOS distribution, with an upgraded kernel on the original OS, supporting a wider range of storage types. It greatly optimizes memory usage of system components, reducing their memory occupation.

Version Check Methods

After logging into the pod, execute the following command to view the host OS kernel version(5.4.241-1.0017):
# uname -a
Linux <pod-name> 5.4.241-1.0017.10.eks.8.tl4

New Features

Mitigated unresponsiveness of the machine that is caused by memory inadequacy. It will trigger cgroup OOM kill timely to prevent the machine from entering the unresponsive state (nodelost state) when the memory in the pod is nearly reached.
Added the support for Cloud Object Storage (COS). For the operation guide, see Using COS.
Added the support for Ceph File System (CephFS).

Optimized Features

The kernel version was upgraded from 5.4.119-1.0009 to 5.4.241-1.0017.
containerd was upgraded from v1.4.3 to v1.6.9.
The GPU driver was upgraded from 470 to 535, supporting CUDA version upgrade from up to 11.4 to 12.2.
The systemd software package version was updated from 239 to 255.
The dbus software package version was updated from 1.12.8 to 1.14.8.

Other Notes

To try the operating system in advance, you can submit a ticket for application.
To upgrade a running pod to the new OS version, you need to rebuild the pod first.
If you have specified a specific OS version through the annotation (eks.tke.cloud.tencent.com/eklet-version), you need to remove that annotation to make the new OS version take effect.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan