Constraints

This section describes the constraints on using CCI.

Constraints on CCI Instances

The following table lists the constraints on CCI instances.

Item	Constraint
Account for creating CCI instances	The account must have complete real-name authentication.
Resource quotas of a single account	Log in to the Huawei Cloud management console and choose Resources > My Quotas > Quotas to view the total quota and usage of each resource. NOTE: If a quota cannot meet your business requirements, you can increase the quota. For more information on quotas, see Quotas.
Number of vCPUs per CCI instance	0.25 to 32 vCPUs, or 48 vCPUs or 64 vCPUs
Supported OS	Only Linux
Network type	Only VPC

Constraints on Kubernetes

For security purposes, CCI does not support Kubernetes functions listed in the following table.

Unavailable Function	Description	Recommended Alternative Solution
hostPath	Mounts a file on the local host to a pod.	EVS disks or SFS file systems
hostNetwork	Maps the host port to a pod.	Load balancing (type=LoadBalancer)
DaemonSet	Ensures that there is only one copy of pod on each node.	Deploy multiple containers in a pod in the form of sidecar.
Privileged permission	Allows a container to have the privileged permission.	Use the security context to enable the privileged mode for the pod.
Service with type set to NodePort	Maps the host port to a pod.	Load balancing (type=LoadBalancer)

Constraints on Pod Specifications

For pod pricing details, see Product Pricing Details.

The pod specifications you select must meet the following requirements.

**Table 1** Requirements on pod specifications
Item	Value Range
Number of vCPUs	0.25 to 32 vCPUs, or 48 vCPUs or 64 vCPUs The vCPUs of a single container must be an integer multiple of 0.25.
Memory	1 GiB to 512 GiB The memory must be an integer multiple of 1 GiB.
vCPU/memory ratio	Between 1:2 and 1:8
Containers in a pod	A maximum of five containers A single container has at least 0.25 vCPUs and 0.2 GiB of memory. The maximum resource specification of a container is the same as that of a pod.
All containers in the pod and init containers	The request and limit of the two types of containers are the same.

GPU-accelerated pods are temporarily unavailable because GPU resources are insufficient.
For more information, see Calculating Pod Specifications.
Init containers are specialized containers that run before application containers startup in a pod. For details, see Initializing a Container.

Constraints on Pod Storage Space

If no EVS disk is mounted, application data is stored in the rootfs of the container. The following table lists the storage space limit of each type of pod.