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 instancePulling images from self-built image registries during instance creation
Copy page
Download PDFCreating an instance
Pulling images from self-built image registries during instance creation
Copy pageDownload PDFPulling images from self-built image registries during instance creation
VCI allows you to pull images from self-built image registries. When you pull images from a self-built image registry, image pulling may fail due to protocol differences or certificate verification failures. This topic describes how to create VCIs or image caches by pulling images from a self-built image registry when the self-built image registry uses HTTP and self-signed certificates.
Feature description
VCI supports self-built image registries in the following scenarios:
- Pull images (including using image caches) during the creation of instances.
- Create image caches.
VCI allows you to pull images from self-built image registries by using annotations. The following table describes annotations. For more information about VCI annotations, see Pod annotation descriptions.
Annotation key | Annotation sample value | Description | Required |
Annotation key | Annotation sample value | Description | Required |
vci.volcengine.com/insecure-registries | "registry1,registry:5000,registry:80" | When you pull images from an image registry that uses a self-signed certificate, certificate verification fails, which results in image pull failure. You can skip TLS authentication to resolve this issue. Separate multiple image registries by commas (,). If the address of the image registry contains a port number, you also need to enter the port number. | no |
vci.volcengine.com/plain-http-registries | "registry1-http,registry-http:5000,registry-http:80" | Specify HTTP-accessible image registries, separated by commas (,). If the image registry address includes a port number, enter the port number as well. | no |
Usage limits
- You can use this method only by using YAML instead of the console.
- Image caches can only be created automatically or manually, not via the CRD method. For details about image caches, see VCI image caches.
Procedure
The following sample code shows how to create a Deployment. For detailed instructions, see Creating general-purpose instances by specifying container vCPUs and memory. For more information about creating VCIs, see Creating instances.
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 instance family of VCI.
"vci.volcengine.com/insecure-registries": "registry1,registry:5000,registry:80" # Specify image registries that skip TLS authentication and separate multiple image registries by commas (,).
"vci.volcengine.com/plain-http-registries": "registry1-http,registry-http:5000,registry-http:80" # Specify image registries that are accessed via HTTP and separate multiple image registries by commas (,).
labels:
app: nginx
spec:
containers:
- name: nginx
image: doc-cn-beijing.cr.volces.com/vke/nginx-demo:v1.0 # The address of your self-built image registry. If you need to use a public image, make sure that the cluster can access the public network.
ports:
- containerPort: 80
resources:
requests: # Specify the container CPU and memory.
cpu: "500m"
memory: "1024Mi"
limits:
cpu: "1"
memory: "2048Mi"
Last updated: 2026.08.19 17:56:46
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
