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 diagnosisPod diagnosis
Copy page
Download PDFFault diagnosis
Pod diagnosis
Copy pageDownload PDFPod 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 pod 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 Pod diagnostic task.
- ParameterDescriptionParameterDescriptionDiagnosis typeSpecify the type of resource to be diagnosed. For this example, select Container group.NamespaceSelect the namespace where the pod is located.PodsIn the All container groups list on the left side, select the pods on which you need to perform diagnosis, and add them to the Select container groups 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 pod. 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
tip
The diagnostic items slightly vary based on different pod types, such as pods and elastic pods. The diagnostic items displayed in the console shall prevail.
Pod load
Diagnostic item | Check content | Fix suggestions | Reference |
Diagnostic item | Check content | Fix suggestions | Reference |
Pod memory utilization | Check whether the pod memory utilization is greater than 85%. Excessive memory load may cause OOM errors, which affect normal business operations. | Increase the number of pod instances or configure autoscaling. | |
Pod CPU utilization | Check whether the Pod CPU utilization is greater than 80%. Excessive CPU load may cause CPU preemption, which affects normal business operations. | | |
Pod status
Diagnostic item | Check content | Fix suggestions | Reference |
Diagnostic item | Check content | Fix suggestions | Reference |
Pod container image download failures | Check whether the pod image is downloaded. | Check the status and logs of the pod. | |
Pod initialization status | Check whether the pod is initialized as expected. | Check the status and logs of the pod. | |
Pod scheduling status | Check whether the pod can be scheduled as expected. | Determine the reason why the pod cannot be scheduled, such as insufficient resources and node affinity. | |
Pod container restart statistics | Check the number of times that the pod restarts. Frequent restarts indicate abnormal pod operation. | Check the status and logs of the pod. | |
Whether the image cache is available | Enable the image cache feature and check whether it is ready. It can be in the following abnormal status:
| Check whether the image cache is in a normal status. If you encounter an issue, submit a ticket for processing. | |
Validity of pod container image Secrets | Check whether the Secret that is configured when the pod pulls images by using the password-free add-on is valid. If the Secret is invalid, the pod will be unable to pull images by using the secret-free add-on. | Check the status and logs of the pod. |
Last updated: 2026.07.23 17:53:05
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
