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 AnnouncementsAnnouncementsBasic Monitoring Architecture Upgrade

Basic Monitoring Architecture Upgrade

PDF
Focus Mode
Font Size
Last updated: 2024-12-13 15:46:01

Background

TKE will be upgraded to provide more stable basic monitoring services and improve the availability of monitoring data, alarming, and HPA scaling. The upgrade falls into three phases, that is, deploying the new version of the monitoring service add-on, switching the add-on version, and deactivating the earlier version, without affecting the services.

Operation Details

Phase 1. Deploying the monitoring service add-on

The tke-monitor-agent monitoring data collection add-on will be installed under the kube-system namespace of your cluster. The agent will use less than 70 MB memory and 0.01 CPU cores on each node. For add-on details, see Description of tke-monitor-agent.

Phase 2. Switching the add-on version

This phase will be performed one week after the new version of the add-on is deployed to ensure the data source stability.
Note:
If a Kubernetes cluster on v1.8 or later is used, a Service and Endpoint named metrics-service will be created under the kube-system namespace and point to the metrics-server maintained on the container side.
The hpa-metrics-service in the cluster will point to the new data source. If apiservice v1beta1.metrics.k8s.io uses the default kube-system/hpa-metrics-service data source provided by the container, and the Kubernetes cluster is on v1.8 or later, it will switch to the more stable data source kube-system/metrics-service.
apiservice v1alpha1.monitor.tencent.io will be added to support TKE virtual nodes in reporting monitoring data and querying the monitoring data of Pods on each node.

Phase 3. Deactivating the earlier version of the monitoring add-on

This phase will be performed one week after the add-on version is switched.
Previous Topic: Notice on TPS Discontinuation on May 16, 2022 at 10:00 (UTC +8)Next Topic: Starting Charging on Managed Clusters

Help and Support

Was this page helpful?

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

Feedback