Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
Document
Volcengine Kubernetes Engine
What's New
History feature release notes
Kubernetes version release notes
Containerd runtime release notes
Add-on release notes
Monitoring add-ons
Scheduling add-ons
DNS add-ons
Security add-ons
GPU add-ons
Sandbox add-on
Security announcements
Product Announcement
Historical announcements
Overview
Getting started
User guide
Clusters
Creating clusters
Connecting to clusters
Upgrading clusters
Node pool
Creating node pools
Scaling out/in node pools
Nodes
Authorization management
Image
Namespaces
Networking
Cluster network
Container Network
Service
LoadBalancer
CLB
Ingress
APIG Ingress
ALB Ingress
Customize ALB Ingress forwarding rules
Certificate and security
CLB Ingress
Nginx Ingress
Gateway API
Workloads
Creating workloads
Configure workloads
Pods
Configuration management
Image acceleration
Storage
FSX client
EBS Volumes
TOS Volumes
NAS volumes
FSX access methods
NFS access methods
EFS volumes
vePFS volumes
FSX access methods
vePFS Client access methods
NFS access methods
CloudFS volumes
Local volumes
Autoscale
Node autoscaler
Workload autoscaler
Horizontal Pod Autoscaler (HPA)
Cron Horizontal Pod Autoscaler (CronHPA)
Intelligent Horizontal Pod Autoscaler (IHPA)
Horizontal Pod Autoscaler based on event-driven (KEDA)
Add-on management
Network add-ons
Storage add-ons
Monitoring add-ons
Scheduling add-ons
DNS add-ons
GPU add-ons
Core add-ons
Sandbox add-on
Upgrading add-ons
Heterogeneous computing
NVIDIA GPU
mGPU scheduling
RDMA high-performance computing
Scheduling management
Topology-aware scheduling
QoS-aware scheduling
Observability
Log management
Basic observation
Setup & Configuration
Cluster observation
Storage observation
Other observation
Using metrics
Full stack observation
Alert management
Diagnosis and inspection
Node check and self-healing
Application center
Backup center
Stability
Large-scale cluster management
Best practices
Authorization
Clusters
Nodes and node pools
Networking
Storage
Scheduling
Observability
Solution
Security and compliance
API reference
Cluster management
NodePool management
Node management
Virtual nodes management
Add-on management
Tag management
Access policy management
Instance images management
Cloud native observability
Inspection and diagnosis
Task management
Volcengine Container Instance
Appendix
SDK reference
Development guide
Terraform
FAQs
General FAQs
Cluster FAQ
cluster management
cluster network
cluster upgrade
Node and Node pool FAQs
Authorization FAQs
Workload FAQs
Service and Ingress FAQs
Storage FAQs
Heterogeneous computing FAQs
Observability FAQs
Quota FAQs
Add-on FAQs
Cloud-native AI
ServingKit
LLM applications
ComfyUI application
Deploying the Al inference application through Helm
Deepseek practices
Qwen practices
Kimi practice
Seed practices
Best practices
DeepSeek model deployment
GLM model deployment
MiniMax model deployment
Qwen model deployment
Kimi model deployment
Volcengine Container Instance
What's new
Historical feature release notes
Product Announcement
Overview
Billing
User guide
Integrating with VCI
Virtual node
VKE cluster uses virtual nodes
Self-managed/third-party cluster uses virtual node
Creating an instance
General purpose instance
GPU-accelerated computing instance
VCI Agent Sandbox
Startup acceleration
E2B-based management
Upgrade guide
Networking
Monitoring
Scheduling
Container configuration
VCI Image Cache
Best practices
Security and compliance
FAQs
- Documentation
Volcengine Kubernetes EngineVolcengine Kubernetes EngineUser guideDiagnosis and inspectionFault diagnosisNode pool diagnosis
Copy page
Download PDFFault diagnosis
Node pool diagnosis
Copy pageDownload PDFNode pool diagnosis
Cluster diagnosis helps you identify risks in various resources within VKE clusters, such as node pools, nodes, and pods. This topic describes how to configure the node pool diagnosis feature.
Configuring diagnosis
- Log in to the VKE console.
- In the left navigation pane, click Cluster. Click the target cluster name to go to the management page of this cluster.
- In the left navigation pane, click Diagnosis. On the page that appears, click Create diagnosis task to configure a node diagnostic task.
- ParameterDescriptionParameterDescriptionDiagnosis typeSpecify the type of resource to be diagnosed. For this example, select Node pool.Node pool managementIn the All node pools list on the left side, select the node pools on which you need to perform diagnosis, and add them to the Selected node pool list on the right side.
- Click Confirm to complete the configuration. The system will start the diagnosis and generate a diagnostic report.
Viewing diagnostic results
After the diagnostic task is complete, if it is in the Anomaly state, it indicates that risks exist in the node pool. You can click View details in the Actions column that corresponds to the target diagnostic task to view the diagnostic report.
The diagnostic result will display all diagnostic items, including successful, failed, and warning ones. You need to view these items on the Pending tab and resolve the issues.
Downloading diagnostic reports
After the diagnostic task is complete, you can download the diagnostic report in PDF format.
- After the diagnostic task is complete, click View details in the Actions column that corresponds to the target diagnostic task to view the diagnostic result.
- Click Download the report in the upper-right corner to download the diagnostic report in PDF format.
Diagnostic item descriptions and fix suggestions
Diagnostic item | Check content | Fix suggestions | Reference |
Diagnostic item | Check content | Fix suggestions | Reference |
Scale-out records within the last six hours | Check whether the cluster failed to scale out in the last six hours. Scale-out failure may result in insufficient resources in the cluster, which affects normal business scheduling. |
| |
Scale-in records within the last six hours | Check whether the cluster failed to scale in within the latest six hours. If the cluster failed to scale in, idle resources may exist in the cluster, which will result in resource waste. |
| |
Status check of node pool | Check whether the node pool is not in the Running state. If the node pool is in an abnormal status, the resources in the node pool will become unavailable. | Troubleshoot based on the node pool status. | |
Cluster status | Check whether the cluster is not in the Running state. If the cluster is in an abnormal status, the resources in the node pool will become unavailable. |
| |
ECS inventory | Check whether the ECS instance type used in the current node pool has sufficient stock. If the ECS instance type is sold out, nodes of this type cannot be created, which results in node pool scale-out failure. |
| |
EIP capacity | Check whether the remaining EIP capacity is less than 1. If EIPs are insufficient and the automatic binding of EIPs to nodes is enabled for the node pool, the node pool will fail to scale out. | ||
VKE cluster node quota | Check the node quota of the cluster. If the quota is used up, nodes will be unable to be added to the node pool, which results in scale-out failure. | ||
Remaining available IPs in the VPC subnet | Check whether the number of remaining IP addresses in the VPC is less than 5. If IP addresses in the VPC are used up, ECS instances cannot be created, and the node pool will fail to scale out. | None | None |
VPC security group | Check the VPC security group. The configuration of security group rules affects internal network connectivity within the cluster. | None | |
Whether autoscaling is enabled | Check whether autoscaling is enabled for the node pool. If autoscaling is not enabled, the nodes in the node pool may be overloaded and cannot be autoscaled. | Enable the autoscaling feature for the node pool. | |
CA add-on status | Check whether the cluster autoscaling add-on (cluster-autoscaler) is installed in the cluster, and whether the add-on is in a normal status. If the add-on is not installed or in an abnormal status, the node pool cannot be autoscaled. | Install the cluster autoscaling add-on (cluster-autoscaler) and make sure that the add-on works as expected. |
Last updated: 2026.07.23 17:53:05
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
