Help Center/ Cloud Container Instance (CCI)/ Service Overview/ Notes and Constraints
Updated on 2025-06-16 GMT+08:00
View PDF
Share

Notes and Constraints

This topic describes the constraints on using CCI 2.0.

Image Pull Constraints

VPC endpoints are required to pull images from SWR. Currently, VPC endpoints cannot be created automatically. Therefore, before using CCI 2.0, you need to manually create VPC endpoints. If there are no VPC endpoints, an error message will be displayed indicating that the image fails to be pulled when you create a pod or Deployment.

You need the following VPC endpoints:

  • To pull images from a repository of SWR Enterprise Edition, you need to purchase a VPC endpoint for OBS.
  • To pull images from the SWR public image repository, you need to purchase a VPC endpoint for SWR and a VPC endpoint for OBS.

    For details, see Purchasing VPC Endpoints.

Constraints on Pod Specifications

The following table lists the pod specifications.

Table 1 Supported pod specifications

Container vCPUs

Container Memory (GiB)

0.25

0.5, 1, and 2

0.5

0.5, 1, 2, 3, and 4

1

1 to 8 (increment: 1 GiB)

2

2 to 16 (increment: 1 GiB)

4

4 to 32 (increment: 1 GiB)

8

8 to 64 (increment: 4 GiB)

16

16 to 128 (increment: 8 GiB)

32

32, 64, 128, and 256

48

96, 192, and 384

64

128, 256, and 512

For pods running on CCI 2.0, the OS and CCI occupy some underlying resources. In some extreme scenarios, the actual memory usage of a pod may not reach the memory in the pod specifications. If you need to use all resources defined in the specifications, CCI 2.0 allows you to reserve system overhead. For details, see Increasing Reserved System Overhead.

Constraints on Pod Storage Space

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

Table 2 Default storage space of each pod

Pod Type

Storage Space

General

30 GiB

As the OS and CCI occupy some underlying resources, the disk usage cannot reach the default storage space in actual use. In addition, the larger the pod specifications you select, the more the system resources are occupied. By default, if the ephemeral storage of a pod exceeds 20 GiB, you can expand the pod storage as needed. For details, see Adding Ephemeral Storage Capacity

Constraints

  • For Services of the LoadBalancer type, only dedicated load balancers are available. If a Service of the LoadBalancer type is used, the pods can have IPv4 IP addresses.
  • If the CCE Cloud Bursting Engine for CCI add-on is used to schedule the workloads to CCI 2.0, dedicated load balancers can be configured for ingresses and Services of the LoadBalancer type. The CCE Cloud Bursting Engine for CCI add-on does not support Services of the LoadBalancer Services if its version is earlier than 1.5.5.