Docs

Volcengine Kubernetes Engine

Overview

Limits

This topic describes limits of using VCI.

VCI limits

Warning

If you reach the quota limits and need to increase the quotas, confirm the number of pods in the Pending state caused by insufficient quotas in the cluster.

When excessive pods in the Pending state exist in the cluster, we recommend deleting pods in this state before increasing the quota or gradually increasing the quota. This prevents a large number of pods in the Pending state from being scheduled at the same time after the quota is increased, which may cause excessive loads on services suddenly and affect business availability.

Item			Description	Method of applying for more quota
Volcano Engine root user accounts for creating VCIs			The root user must complete real-name authentication. The account balance is not less than CNY 100 when vouchers are included and is not zero when vouchers are excluded.	No
Supported VKE cluster types			Clusters with the VPC-CNI network model Clusters with the Flannel network model	No
Maximum number of VCIs per virtual node in a VKE cluster			3,000	Submitting a ticket
Number of vCPUs allowed per AZ			The limits for different specifications vary by region and AZ. Refer to the displayed quota in the Quota center.	Submitting an application in the quota center
Number of GPU cards allowed per AZ	vci.gni3	0	Submitting a ticket
		vci.gni2	0	Submitting a ticket
		vci.ini2	0	Submitting a ticket
		vci.g1v	0	Submitting a ticket
Maximum number of data volumes allowed per VCI			16 disks (including one system volume)	No
Maximum number of containers supported per VCI			20	No
The maximum number of layers on a single image			50	No
Supported container operating system types			Linux	No
Supported Kubernetes versions			This limit aligns with the Kubernetes version limit of VKE. For details, see Kubernetes version release history.	No
enableServiceLinks			When a single namespace of a cluster has 100 Services or more, VCI will disable the enableServiceLinks capability (enableServiceLinks:false) to override the Kubernetes-native enabling of enableServiceLinks in the Pod.Spec.	Submitting a ticket

Kubernetes limits

Based on the Virtual Kubelet technology from the Kubernetes community, VCI achieves seamless integration with Kubernetes through virtual nodes. Therefore, VCIs do not run on a centralized physical node, but are distributed across the entire cloud resource pool.

Due to restrictions imposed by virtual nodes and public cloud security considerations, VCI has the following limitations on Kubernetes:

Unsupported feature	Description	Recommended alternative solution
DaemonSet	Does not support using DaemonSet to deploy static pods on the host machine of containers.	Deploy multiple images in a pod using the Sidecar form.
HostPath	Does not support mounting local host files into containers via HostPath.	Use EmptyDir, cloud disks, or NAS file systems to meet local storage requirements.
Privileged permission	Does not support enabling the privileged mode for containers via privileged permissions.	Use security contexts to add Capabilities (limited support) to pods, and leverage Docker Container Capabilities to control permissions, achieving outcomes similar to the Privileged mode.
NodePort Service	Does not support mapping host ports to containers via a NodePort Service.	Use a Service of type LoadBalancer to enable external access to cluster services.
HostNetwork	Does not support mapping host ports to containers via HostNetwork.	Use a Service of type LoadBalancer to enable external access to cluster services.
NetworkPolicy	Does not support using NetworkPolicy to implement pod isolation and control network traffic.	Use pod security groups to define access rules.
Node-related management and monitoring	Does not support worker node-related capabilities.	VCI does not expose physical nodes, so no alternative is available.

Port usage

The following table shows the port used by VCI. When deploying a service, avoid using the following port:

Port	Description
1025	Port used by VCI. Used by APIs such as gpu metrics.

Viewing and applying for quotas

VCI allows you to view the VCI resource usage in the VKE console and increase quotas of certain resources.

In the left navigation bar, click Volcengine Container Instance > Container instance overview.

On the Container instance overview page, view the quota usage of VCIs in each AZ within a region. To increase the quota, click Apply for quota.

On the VKE quota page in the Quota Center, view the quota parameters of the VCI and submit a request to increase adjustable quotas.

Last updated: 2026.07.24 16:18:01