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 by ignoring specific container resource requirements
Copy page
Download PDFCreating an instance
Creating instances by ignoring specific container resource requirements
Copy pageDownload PDFCreating instances by ignoring specific container resource requirements
VCI allows you to ignore the resource requirements of specific containers during the creation of instances. In this way, exclusive resources are not allocated to some containers that do not affect your business in certain scenarios.
Feature description
You can configure the following environment variable for a container in a VCI pod. VCI will ignore the resource requests of the container during resource adjustment.
env:
- name: "__VCI_RESOURCE_IGNORE__" # Ignore the resources of the container during automatic specification matching.
value: "TRUE"
If a VCI pod has n containers, when VCI matches instance (pod) specifications, it traverses the n containers in the following priority order and matches only one of the following cases:
- If "__VCI_RESOURCE_IGNORE__"="TRUE" is configured, the resource requirements of the container are skipped.
- If a resource (such as CPU, memory, and GPU) is configured with a limit, the limit value of the container is added to the resource requirement.
- If a resource is configured with a request, the request value of the container is added to the resource requirement.
tip
VCI matches instance specifications based on the accumulated values of CPU, memory, and GPU. For more information about specification calculation and matching, see Instance specification normalization.
Limits
- The method described in this topic applies to scenarios such as creating general-purpose instances by specifying container vCPUs and memory and creating GPU-accelerated instances based on specified container GPU resources.
- After the resource requirements of specific containers are ignored, the total resources provided by the matched VCI instance specification may be less than the total resources declared by all containers in the pod. For example:
- If CPU and memory resource requirements are ignored, CPU and memory resources are shared among containers, and multiple containers may compete for resources.
- If GPU resource requirements are ignored, GPU resources cannot be shared among containers. In this way, the VCI pod will fail to be created (data plane failure) if its matched instance specification has fewer GPUs than the total declared by all containers.
- We recommend that you use this feature in the following way:
- For CPU and memory, you can ignore the resource requirements of specified containers. In this way, multiple containers will compete for resources. In addition, you can specify the limit for each pod. This prevents containers without a configured limit from occupying resources for other containers, improving resource utilization within the pod.
- For GPU, we recommend that you configure the environment variable only for containers that do not require GPU resources, such as sidecar containers. In this way, other containers can use as much CPU and memory as possible.
Prerequisites
A cluster for VCI applications has been created. For details, see Using VCI in VPC-CNI clusters and Using VCI in Flannel clusters.
Procedure
Using the Kubernetes approach
The following sample code shows how to create a Deployment.
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
labels:
app: nginx
spec:
replicas: 2
selector:
matchLabels:
app: nginx
template:
metadata:
annotations:
vke.volcengine.com/burst-to-vci: enforce # Force the use of VCI.
labels:
app: nginx
spec:
containers:
- name: nginx1
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. If you need to use a public image, make sure that the cluster can access the public network.
resources:
limits:
cpu: "2000m"
memory: "4096Mi"
- name: nginx2
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. If you need to use a public image, make sure that the cluster can access the public network.
resources:
limits:
cpu: "1000m"
memory: "2048Mi"
env:
- name: "__VCI_RESOURCE_IGNORE__" # Ignore the resources of the container during automatic specification matching.
value: "TRUE"
restartPolicy: Always
Creating instances by using the console
- Basic information: Select Volcengine Container Instance for the Computing power type parameter.
- Container configuration: Enable Ignore resource alignment in the ResourceQuota section.
Last updated: 2026.09.03 15:56:09
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
