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 guideStabilityBasic stability capability configuration
Copy page
Download PDFStability
Basic stability capability configuration
Copy pageDownload PDFBasic stability capability configuration
This topic mainly introduces configurations and operational recommendations related to basic stability for VKE applications.
Background information
Growing containerized workloads can bring greater pressure and more complex challenges to your business system. Stability optimization helps ensure that the system can adapt to increasing demands and support business expansion. VKE, with workloads and Kubernetes clusters as its core, can help you improve business stability without requiring intrusive modifications.
This topic covers basic stability optimization. For more information on stability optimization, see the following topics:
Basic stability
Category | Item | Description | Related documentation |
Category | Item | Description | Related documentation |
Cluster planning | Configuring control plane high-availability | Build a highly available control plane by configuring subnets in multiple availability zones. | |
Add-on management | Using standard add-ons provided by VKE | Avoid using third-party tools for business management. Always deploy standard add-ons provided by VKE. | |
| Preferring VCI-based deployment | To avoid add-on resource overloading and subsequent impact on application functionality, we recommend that you preferentially use VCI-based deployment as the deployment option when deploying add-ons (that is, deploying add-ons using VCI resources). | |
Node pool management | Managing nodes by using node pools | Manage a group of node resources in a cluster as a node pool. | |
| Using managed node pools | It is recommended to use managed node pools to manage node resources. Managed node pools provide common fault detection and self-healing for nodes. | |
| Monitoring and increasing quotas | Quota limits apply to VKE resource usage. When the quota consumption is high, increase the quota in time. You can also configure alerting in the Quota Center so that you can receive notifications before quota depletion and act accordingly in advance. | |
Enabling observability | Integrating metric monitoring and alerting | Use cloud native observability (basic observability and full-stack observability) or Cloud Monitor to implement collection, monitoring, and alerting of clusters, basic resources, and application metrics. | |
| Integrating logging | Collect logs of the control plane, workloads, add-ons, and cluster events into TLS to achieve log and event persistence. | |
| Enabling cluster auditing | Enable cluster auditing to collect cluster operation logs to TLS. | |
| Enabling add-on monitoring | Monitor metrics of common add-ons, such as Ingress, DNS, and CNI. | |
| Enabling network and application monitoring | Monitor Layer 4/Layer 7 network traffic metrics and visually manage upstream and downstream calls to achieve network and application observability. | |
| Enabling cluster inspection | Cluster inspection helps identify potential risks in clusters. | |
| Enabling diagnosis | Fault diagnosis provides rapid diagnosis capabilities for cluster resources, such as node pools, nodes, and pods. |
Last updated: 2026.07.24 14:51:36
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
