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 inspectionCluster inspectionConfiguring cluster inspection
Copy page
Download PDFCluster inspection
Configuring cluster inspection
Copy pageDownload PDFConfiguring cluster inspection
Cluster inspection helps you identify risks within VKE clusters, such as configuration risks, resource anomalies, insufficient quotas, and resource utilization. This topic describes how to configure cluster inspection.
Configuring periodic inspection
- Log in to the VKE console.
- In the left navigation bar, click Cluster.
- In the cluster list, click the target cluster.
- In the left navigation bar of the cluster management page, click Cluster health check. On the page that appears, click Health check settings.
- Next to Scheduled check, click the
icon. In the pop-up dialog box, enable scheduled inspection and specify the time at which periodic inspection is performed.
- Click Confirm. The system will execute the inspection task at the specified time and generate an inspection report.
Configuring manual inspection
- Log in to the VKE console.
- In the left navigation bar, click Cluster.
- In the cluster list, click the target cluster.
- In the left navigation bar of the cluster management page, click Cluster inspection.
- Click Start health check to perform a manual inspection and generate an inspection report.
Obtaining inspection results
Viewing inspection reports
After the scheduled or manual inspection task is complete, if the current inspection task is in the Exception state, it indicates that risks exist in the cluster. You can click View details in the Action column that corresponds to the target inspection task to view the inspection report.
The inspection result will display all inspection items in the current cluster, including successful and pending ones. You need to view the items on the Pending tab and resolve the issues. For details on fixing specific issues, see Inspection item descriptions and fix suggestions.
Downloading inspection reports
After the inspection is complete, you can download the inspection report in PDF format.
- After the inspection task is complete, you can click View details in the Action column that corresponds to the target inspection task to view the inspection report.
- Click Download the report in the upper-right corner to download the inspection report in PDF format.
Subscribing to inspection reports
The inspection report subscription feature allows inspection reports to be sent to the target email address or Lark group at a specified time. The inspection reports are sent in the following logic:
- The latest inspection reports within the last 24 hours will be sent, including reports generated by both periodic and manual inspections.
- If no inspection reports are generated in the last 24 hours, a notification will be sent, and we recommend enabling scheduled inspection.
Perform the following steps to subscribe to inspection reports:
- In the left navigation bar of the cluster management page, click Cluster health check and click Health check settings.
- Next to Inspection report, click the icon to enable inspection report subscription and specify the related parameters.
Parameters | Description |
Parameters | Description |
Subscription | Whether to enable inspection report subscription. To subscribe to inspection reports, enable this feature. |
Time to push (every day) | Select the desired push time for the inspection report from the drop-down list and then click Confirm. |
Receiver | Specify the method and recipient for receiving inspection reports. Valid values:
warning When you use Larkbot to receive inspection reports, you cannot use custom bots for which keys are enabled. Therefore, do not enable the signature verification feature of Larkbot. |
- Click Confirm.
Configuring inspection silence
If some inspection items in your cluster do not meet the inspection requirements but can be temporarily ignored, you can configure an inspection silence policy. The policy is used to silence specified resources or inspection items to prevent noise interference during each inspection.
- In the left navigation bar of the cluster management page, click Cluster health check. On the page that appears, click Health check settings.
- Click Create silence strategyCreate silence policy to configure an inspection silence policy.
- ParameterDescriptionParameterDescriptionNameSpecify the name of the inspection silence policy.DescriptionEnter the description of the inspection silence policy.Matching rules
- Silenced for: Configure the matching dimension for inspection silence. Valid values:
- Check item: Inspection silence is performed based on inspection items and resources. The default inspection result for silenced rules or resources is Passed, which ensures that their abnormal status does not interfere with the inspection result.
- Resource: Inspection silence is performed based on the resources in the cluster. The default inspection result for silenced rules or resources is Pass, which ensures that their abnormal status does not interfere with the inspection result.
- Check item: Configure the check items that need to be silenced.
- Specify resources: Specify the resources that need to be silenced. Common cluster resources, such as pods, nodes, Deployments, and StatefulSets, are supported.
- Click Confirm.
Last updated: 2026.07.24 14:51:36
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
