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

Viewing Monitoring Metrics of Control Plane Components in a TKE Cluster

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-04-29 10:56:12

Application Scenario

Tencent Kubernetes Engine (TKE) is a managed Kubernetes service. TKE automatically manages the availability and scalability of Kubernetes control plane nodes, which are responsible for scheduling containers, managing application availability, storing cluster data, and execute other critical tasks. However, the behavior or configuration of specific workloads may increase the load on the control plane, resulting in performance degradation. In such cases, accessing key control plane metrics and monitoring charts enables cluster administrators to quickly detect and solve issues of workloads running on a cluster. For example, worker nodes with insufficient resources may affect Pod scheduling of the scheduler. To detect scheduling issues promptly, cluster administrators need to access scheduler metrics to view Pods pending processing and receive notifications in a timely manner. In addition, there are a large number of control plane metrics. Even experienced administrators face the challenge of selecting the proper monitoring metrics and creating valid monitoring charts.
TKE provides monitoring capabilities for cluster control plane components. It allows cluster administrators to view the performance of the Kubernetes cluster control plane and quickly detect, troubleshoot, and fix issues. TKE clusters provide monitoring charts through TencentCloud Managed Service for Prometheus (TMP).

Prerequisites

The monitoring component clustermonitor has been upgraded to 1.3.2 or a later version.
TMP has been enabled and associated with instances.

Directions

1. Log in to the TKE console, and click Cluster in the left sidebar.
2. Click the ID of the target cluster on the Cluster Management page to enter the cluster details page.
3. Click TMP in the left sidebar.
4. Enable TMP through one-click enable Prometheus monitoring or associating an existing TMP instance.

5. Click Monitoring Detail on the Prometheus Monitoring page, and click Core Component Monitoring.

View the monitoring dashboard for API Server, Scheduler, and Controller Manager.

References

kube-apiserver component: For the metric list and instructions on using the corresponding monitoring dashboard, see kube-apiserver component metric descriptions.
kube-scheduler component: For the metric list and instructions on using the corresponding monitoring dashboard, see kube-scheduler component metric descriptions.
kube-controller-manager component: For the metric list and instructions on using the corresponding monitoring dashboard, see kube-controller-manager component metric descriptions.
For configuration instructions and recommended alarm configurations for collecting metrics of control plane components in TKE clusters (kube-apiserver, kube-scheduler, and kube-controller-manager) by using self-built Prometheus, see User-built Prometheus Collecting Control Plane Monitoring and Alarms.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan