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 guideCreating an instanceCreating instances and configuring proxy cache repositories
Copy page
Download PDFCreating an instance
Creating instances and configuring proxy cache repositories
Copy pageDownload PDFCreating instances and configuring proxy cache repositories
Volcengine Container Instance (VCI) allows you to configure mirror repositories for image repositories. When you pull images, the requested addresses are replaced with those of the mirror repositories.
Background
In user business scenarios, requirements exist for pulling images from overseas repositories or cross-cloud collaboration. VCI provides the mirror repository configuration feature by using the proxy cache capability of Volcano Engine CR. When you use a public overseas image, you can use this capability to directly pull the corresponding image without changing the image address. This meets cross-region business requirements.
tip
Feature description
VCI allows you to configure a mirror repository by using an annotation. The annotation description is as follows:
- Annotation Key: vci.volcengine.com/registry-mirror-config
- Annotation value:
- The parameter value needs to be in JSON format.
- The JSON file format and parameter descriptions are as follows:
- {"mirrors": { // The domain name configurations of the proxy cache repository."docker.io": ["address1.cr.volces.com", "address2.cr.volces.com"], // Map images in the docker.io remote registry to the specified CR proxy registry. Configure this parameter as needed. When you enter multiple domain names of proxy cache repositories, images are pulled from the proxy cache repositories in the listed order."hub.byted.org": ["address2.cr.volces.com"], // Map images in the hub.byted.org remote registry to the specified CR proxy registry. Configure this parameter as needed."*": ["default-address.cr.volces.com"] // Map all types of images to the specified CR proxy registry. Configure this parameter as needed.}，"configs": {"address1.cr.volces.com": { // Configure an access policy for the specified CR proxy registry."auth": {"username": "xxx", // The username used to log in to the CR proxy registry instance."password": "yyy" // The Base64-encoded password used to log in to the CR proxy registry instance.}，"tls": {"insecure_skip_verify": true // Ignore certificate verification when you log in to the CR proxy registry instance. Configure this parameter as needed.}}}}
Procedure
The following content provides an example of how to create a general-purpose VCI. For detailed instructions, see Creating general-purpose instances by specifying container vCPUs and memory.
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.
- A proxy cache repository has been created. For detailed operations, see Creating proxy cache repositories.
Sample code
The following sample code shows how to create a VCI Deployment:
tip
For configuration instructions other than mirror image repository configuration, see Creating general-purpose instances by specifying container vCPUs and memory.
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 a subnet. You can specify multiple subnets within the same availability zone. To do so, separate them with commas (,).
vci.vke.volcengine.com/preferred-instance-family: vci.u1 # Specify the VCI instance family
vci.volcengine.com/registry-mirror-config: |
{
"mirrors": {
"docker.io": ["address1.cr.volces.com", "address2.cr.volces.com"],
"hub.byted.org": ["address2.cr.volces.com"],
"*": ["default-address.cr.volces.com"]
}，
"configs": {
"address1.cr.volces.com": {
"auth": {
"username": "demo-user",
"password": "*****************"
}，
"tls": {
"insecure_skip_verify": true
}
}
}
}
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 the address of the image in your remote registry.
ports:
- containerPort: 80
resources:
requests: # Specify the vCPU and memory of the container
cpu: "500m"
memory: "1024Mi"
limits:
cpu: "1"
memory: "2048Mi"
Last updated: 2026.09.03 15:56:09
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
