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 Container InstanceUser guideVirtual nodeVKE cluster uses virtual nodesManaging virtual nodes
Copy page
Download PDFVKE cluster uses virtual nodes
Managing virtual nodes
Copy pageDownload PDFManaging virtual nodes
This topic describes how to manage virtual nodes by using the VKE console.
Prerequisites
- The vci-virtual-kubelet add-on has been installed in the VKE cluster. For details, see Installing add-ons.
- A subnet for the corresponding availability zone has been created within the VPC to which the VKE cluster belongs. For details, see Creating subnets.
Procedure
- Log in to the VKE console.
- In the left navigation bar, click Cluster.
- On the Cluster page, click the name of the target cluster.
- In the left navigation bar, select Nodes > Virtual node.
- On the Virtual node page, configure and manage virtual nodes, and create a global VCI configuration.
Configuring virtual nodes
To use VCI Pods in a specific availability zone, configure VCI Pod subnets in that availability zone. The system will automatically create virtual nodes in the corresponding availability zone based on the specified subnets.
- On the Virtual node page, click Configure virtual node. Alternatively, in the availability zone list, find the availability zone in which you want to configure virtual nodes and then click Configure virtual node in the Actions column.
- On the Configure virtual node page, configure VCI Pod subnets for virtual nodes in the target availability zone, or update the existing VCI Pod subnets.
Warning
You can delete a specified VCI pod subnet only when it is not used by any VCI pod.
-
- After the configuration is complete, click Confirm to save the configuration. The system will automatically create virtual nodes within the corresponding availability zone based on the specified VCI Pod subnets.
Creating a global VCI configuration
A global VCI configuration can be created by using vci-profile. vci-profile is the configuration file for VCI. It allows you to define unified and globally fixed configurations for VCI resource usage at the cluster or namespace level. For a detailed description, see Using VCI by configuring vci-profile.
Other operations
You can perform other operations on virtual nodes, such as cordoning, label management, taint management, and diagnosis. Find the target virtual node in the virtual node list and in the Actions column, click the ... icon to perform the corresponding operation. For a detailed description, see Managing nodes.
Last updated: 2026.07.24 16:18:06
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
