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, the pod storage capacity of the backend instance is restricted to 20 GiB. To ensure optimal performance, it is best to limit the container image size to 5 GiB or less. Additionally, if a large number of files are generated in the container root directory or emptyDir during runtime, it is advised to use external storage such as SFS, SFS Turbo, or OBS.
If a CCE Autopilot cluster is used, a maximum of 500 pods can be created. Add-on pods may occupy the pod quota. Plan the pod quota properly.
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.

Category	Item	Quota
CCE cluster	Total number of clusters	50
VPC	VPCs	5
	Subnets	100
	Security groups	100
	Security group rules	5000
	Routes per route table	100
	Routes per VPC	100
	VPC peering connections	50
	Network ACLs	200
ELB	Load balancers	50
	Load balancer listeners	100
	Load balancer certificates	120
	Load balancer forwarding policies	500
	Load balancer backend host groups	500
	Load balancer backend servers	500
VPCEP	Endpoints	50
DNS	Private zones	50
DNS	DNS record sets	500