Notes and Constraints

Use Restrictions

• Worker nodes in CCE Autopilot clusters are fully hosted. For this reason, certain features like hostPath and hostNetwork, which rely on node features, are not supported.

  Unavailable Feature	Description	Recommended Alternative Solution
  DaemonSet	Deploys pods on each node.	Deploy multiple images in a pod using sidecars.
  Setting hostPath in a pod	Mounts local files of a node to a container.	Use emptyDir or cloud storage of any type.
  Setting hostNetwork in a pod	Maps a node port to a container port.	Use Services of the LoadBalancer type.
  NodePort Service	Makes a node port open to access containers.	Use Services of the LoadBalancer type.

• When a CCE Autopilot cluster is used, each pod in the workload provides 30 GiB of free disk space by default (maximum IOPS of 2,500 and maximum burst IOPS of 16,000). In addition to the resources reserved for the OS and CCE platform, the total available space for images, containers, and temporary storage is about 20 GiB. If the container image is too large (generally greater than 5 GiB) or a large number of files are created in the container root directory or temporary storage, you are advised to increase the temporary storage capacity of the pod. For details, see "Increasing the Ephemeral Storage Space of a Pod" in the CCE Autopilot User Guide.
• By default, no more than 500 pods can be created in a CCE Autopilot cluster. The add-on instances may occupy some pod quotas. You need to plan the pod quota appropriately. To increase the quota, submit a service ticket.
• If a CCE Autopilot cluster is used, workloads that use Arm images are not supported.

Cloud Product Quota Limits

The table below shows the maximum number of resources that can be created per account in a region.

If your current quota is insufficient, submit a service ticket to request an increase.