- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Clusters
- Workloads
- Network
- Storage
- O&M
- Namespaces
- ConfigMaps and Secrets
- Auto Scaling
- Add-ons
- Helm Chart
- Permissions
- Settings
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- Autopilot Cluster Management
- Add-on Management for Autopilot Clusters
-
Autopilot Cluster Upgrade
- Upgrading a Cluster
- Obtaining Cluster Upgrade Task Details
- Retrying a Cluster Upgrade Task
- Obtaining a List of Cluster Upgrade Task Details
- Performing a Pre-upgrade Check for a Cluster
- Obtaining Details About a Pre-upgrade Check Task of a Cluster
- Obtaining a List of Pre-upgrade Check Tasks of a Cluster
- Performing a Post-upgrade Check for a Cluster
- Backing Up a Cluster
- Obtaining a List of Cluster Backup Task Details
- Obtaining the Cluster Upgrade Information
- Obtaining a Cluster Upgrade Path
- Obtaining the Configuration of Cluster Upgrade Feature Gates
- Enabling the Cluster Upgrade Process Booting Task
- Obtaining a List of Upgrade Workflows
- Obtaining Details About a Specified Cluster Upgrade Booting Task
- Updating the Status of a Specified Cluster Upgrade Booting Task
- Quota Management for Autopilot Clusters
- Tag Management for Autopilot Clusters
-
Chart Management for Autopilot Clusters
- Uploading a Chart
- Obtaining a Chart List
- Obtaining a Release List
- Creating a Release
- Updating a Chart
- Deleting a Chart
- Updating a Release
- Obtaining a Chart
- Deleting a Release
- Obtaining a Release
- Downloading a Chart
- Obtaining Chart Values
- Obtaining Historical Records of a Release
- Obtaining the Quota of a User Chart
- Kubernetes APIs
- Permissions and Supported Actions
- Appendix
-
FAQs
- Billing
- Workloads
- Network Management
-
Storage
- Can PVs of the EVS Type in a CCE Autopilot Cluster Be Restored After They Are Deleted or Expire?
- What Can I Do If a Storage Volume Fails to Be Created?
- Can CCE Autopilot PVCs Detect Underlying Storage Faults?
- How Can I Delete the Underlying Storage If It Remains After a Dynamically Created PVC is Deleted?
- Permissions
- General Reference
Copied.
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 CCE Autopilot is used, each pod in the workload has 30-GiB of free disk space (with an IOPS upper limit of 2,500 and a burst limit of 16,000) by default. 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.
- 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.
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 server groups |
500 |
|
Load balancer backend servers |
500 |
|
VPCEP |
Endpoints |
50 |
DNS |
Private zones |
50 |
DNS record sets |
500 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot