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 guideNetworkingCreating instances by specifying subnets
Copy page
Download PDFNetworking
Creating instances by specifying subnets
Copy pageDownload PDFCreating instances by specifying subnets
VCI supports creating instances using the default subnet or a specified subnet. This topic describes the steps of creating a VCI based on a specified subnet.
Background information
If no subnet is specified, the system uses the default subnet, that is, the pod subnet specified during cluster creation.
Usage limits
- The availability zone to which the subnet belongs must already have a virtual node.
- After the instance is created, its subnet cannot be changed.
Prerequisites
- A cluster for VCI applications has been created. For details, see Using VCI in VPC-CNI clusters and Using VCI in Flannel clusters.
- A VPC and its subnet have been created. For details, see Creating VPCs.
Using the Kubernetes approach
When creating a pod or workload (including Deployment, StatefulSet, Job, or CronJob), specify the subnet by adding an annotation.
The annotation description is as follows.
Annotation key | Annotation sample value | Description | Required |
Annotation key | Annotation sample value | Description | Required |
vke.volcengine.com/preferred-subnet-ids | subnet-3tispp1nai**** | Specify a subnet. tip
| Required for this scenario |
The following sample code shows how to create a Deployment.
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
spec:
replicas: 2
selector:
matchLabels:
app: nginx
template:
metadata:
annotations:
vke.volcengine.com/burst-to-vci: enforce # Force the use of VCI.
vke.volcengine.com/preferred-subnet-ids: subnet-3tispp1nai**** # Specify the ID of the subnet.
labels:
app: nginx
spec:
containers:
- name: nginx
image: doc-cn-beijing.cr.volces.com/vke/nginx-demo:v1.0 # The address and version of the container image. Replace the value with your actual information.
ports:
- containerPort: 80
Using the console
Similarly, specify the subnet by adding an annotation when creating a workload.
The following figure shows how to create a stateless workload (Deployment). The procedure for creating other workloads is similar. For detailed steps of creating workloads, see Workloads.
tip
Querying the subnet of an instance
Obtain the ID of the subnet used by the VCI by using the pod annotation.
Annotation key | Annotation sample value | Description |
Annotation key | Annotation sample value | Description |
vke.volcengine.com/used-subnet-id | subnet-128fhnvjjgg**** | The ID of the subnet to which the instance belongs. |
Last updated: 2026.08.19 17:56:58
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
