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

TKE General Cluster Updates (2025)

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-06-27 16:44:26

June 2025

Update
Description
Documentation
Update of the accidental deletion prevention policies for clusters
Default deny policies are enabled for newly created clusters, targeting "Namespaces with existing Pods cannot be deleted", "CRDs with existing CRs cannot be deleted", "Unblocked Nodes cannot be deleted", "CoreDNS component deletion protection", and "PV in binding state cannot be deleted".
Support for fault experiments by the cluster control plane
Overload and service outage experiments are supported for control plane components (such as etcd, kube-apiserver, and CoreDNS). By conducting periodic experiments and assessments, the capability to respond to control plane failures can be enhanced for the business.
README
Support for custom resource priority for scheduling
PlacementPolicy is a smart scheduling policy provided by TKE to help users manage Pod scheduling behavior more flexibly in a Kubernetes cluster. With PlacementPolicy, users can customize the resource priority according to business needs, preferentially use high-priority nodes during scale-out, and preferentially release low-priority nodes during scale-in. This balances cost reduction and efficiency improvement with business stability.
-
New models for TKE native nodes
TKE native nodes support BF1 and M8 models.

May 2025

Update
Description
Documentation
Support for the custom model scale-out policy by native nodes
The model priority policy is added for native node pools, which supports adjusting the primary and alternative models. If auto-scaling is enabled, the scale-out policy preferentially guarantees the purchase of primary model resources. Alternative models can be selected sequentially only when primary model resources are sold out. The scale-out policy can also be used together with AZ settings to implement dual-dimension scheduling. This effectively solves the problem that models for scale-out do not match expectations due to insufficient resources.
Basic monitoring capability improvement for native nodes
Native nodes support monitoring instance-related metrics, including CPU, memory, network, disk, storage, load balancing, and GPU.
-
Collection configuration improvement for log shipping to Kafka
The original log format and various compression formats are supported if the log consumer is Kafka.
-

April 2025

Update
Description
Documentation
Cluster upgrade capability iteration
TKE supports upgrading the Kubernetes version from 1.28 to 1.30.

New models for TKE native nodes
TKE native nodes support BMIA2m, PNV6, and HCCPNV6 models.
Network monitoring support for workloads
Workloads support monitoring inbound and outbound network traffic and bandwidth.

March 2025

Update
Description
Reference
Cluster storage supports CBS encryption
CBS encryption can protect the data to the maximum extent, requiring no additional modifications on business and user applications. It supports the first-generation and second-generation encryption.
Native nodes support one-click login via OrcaTerm
The one-click login to native nodes via OrcaTerm feature supports SSH and TAT. Users can log in to nodes directly through the TKE console without manually configuring a public IP address or SSH key. This feature optimizes Ops experience, resolves the issue of deep login entry and complex operation procedures for native nodes, and offers a more convenient access method for high-frequency Ops scenarios such as data analysis and AI.
-
Super nodes support multi-path collection
Super nodes can be configured with multi-path for Log collection.

February 2025

Update
Description
Reference
Cluster storage supports GooseFS
By adding Data Accelerator Goose FileSystem (GooseFS) as cluster storage, users can improve the storage access performance for services such as massive data analysis, machine learning, and AI.
-
Cluster control plane component monitoring
TKE provides monitoring capability for cluster control plane components, allowing cluster administrators to view Kubernetes cluster control plane performance, quickly detect, troubleshoot, and fix issues.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan