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

Upgrading tke-monitor-agent

PDF
Focus Mode
Font Size
Last updated: 2025-01-23 17:52:40

September 2022

TKE's basic monitoring add-on tke-monitor-agent will be connected to the cluster add-on management module from 10:00 AM to 22:00 PM on September 27 and 28, 2022, after which you can maintain its lifecycle in the module. This change won't affect your businesses.

Change content

Connect the tke-monitor-agent add-on to the add-on management module to support version upgrades in the console. For detailed directions, see Add-On Lifecycle Management.
Create a secret named sh.helm.release.v1.monitoragent.v1 in the kube-system namespace.

July 2022

TKE's monitoring add-on will be upgraded to a new version from 10:00 AM to 23:00 PM on July 27–29 and August 1–4, 2022. This upgrade will fix some of the known issues and support the collection and reporting of some basic metrics. This change won't affect your businesses. If you don't want to have this change, contact us for assistance.

Change content

Fix the issue where the CPU utilization (usage/request) and CPU utilization (usage/limit) of the Pod are negative values.
Fix the data source configuration issue where the data source of the GPU metric is incorrectly configured, affecting GPU metric pull in GPU scenarios.
Fix the issue of reporting node CPU and memory utilization metrics.
Support the collection of some metrics:
Support the collection of the node CPU/memory packing rate.
Support the collection of metrics for calculating the recommended CPU/memory value and optimizable CPU/memory resources, which will be collected and reported only when the request recommendation add-on is installed.

Troubleshooting

If you encounter any problems during the upgrade, contact us for assistance.

Help and Support

Was this page helpful?

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

Feedback