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

FAQs for Native Nodes

PDF
Focus Mode
Font Size
Last updated: 2025-05-26 17:36:09

Whether Cost Allocation by Tag Is Supported by Native Nodes?

Cost allocation by tag is supported. The tags set for a node pool take effect on all nodes in the pool. Notes:
1. When a native node pool is created, it inherits the cluster tag preferentially by default. Please ensure that the cloud tag key does not conflict with any tag of the cluster.
2. When the cluster tag is updated, it will be synchronized to the native node pool, and to all its native nodes as well.

How Can We Configure System Disk Monitoring Alerts?

1. Log in to TCOP, and choose Alert Management > Policy Management.
2. Click Create New Policy and configure alerts.
3. On the alert configuration page, select Cloud Product Monitoring as the monitoring type, and select either Container Service (2.0)/Node disk information or Container Service (2.0)/Node disk IO as the policy type.
4. Sequentially select Region, Cluster and Node ID, and set the target native node as the alert object, as shown in the following figure:

5. Select Total Disk Capacity, Disk Utilization, and Disk Write Bandwidth as alert metrics, as shown in the following figure:

6. Click Next: Configure Alarm Notification. For alert notification configuration details, see Notification Template.
7. Click Finish.

How Can We View the Resource Quantity of a Container Within Itself?

Background

When viewing container resources in standard containers (for example, with the top command), the resources of the entire machine are visible. This can cause confusion for some monitoring, troubleshooting, and even some businesses (such as deciding the queue length based on certain parameters under proc). The native node image has the capability to control container resource visibility. By mounting cgroupfs to the host directory and then using bind mount to mount the directory's files to the corresponding /proc location in the container during creation, you can view the container's own resource quantity within itself. That is, commands like free, top, and loadavg within the container will display the container's own values.

Usage

You need to set the following annotation on the pod:
Field annotation
Meaning
cloud.tencent.com/cgroupfs="* "
This means all containers within the pod apply the cgroupfs capability.
cloud.tencent.com/cgroupfs="container1,container2"
This means that only container 1 and container 2 in the pod apply the cgroupfs capability.
Note:
This feature requires the containerd version to be later than 1.4.3-tke.3 or 1.6.9-tke.3.


Help and Support

Was this page helpful?

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

Feedback