- 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
Show all
Function Overview
-
CCE Autopilot
-
CCE Autopilot is a serverless Kubernetes service provided by CCE. It allows you to run containerized applications without the need to worry about the O&M.
Compared with CCE standard and Turbo clusters, CCE Autopilot clusters have the following advantages:
- Serverless product: Clusters are fully managed. You do not need to deploy, manage, or maintain nodes. This makes CCE Autopilot easy to use and saves O&M costs.
- Resource pooling: A serverless converged resource pool is used to manage resources such as vCPUs, memory, and GPUs, reducing resource fragments and enabling on-demand use and pay-per-use billing of container resources.
- Comprehensive performance optimization: Resource pool resources are pre-provisioned dynamically so that workloads can automatically be scaled in seconds.
By using CCE Autopilot, you can deploy applications without purchasing and maintaining nodes, or planning the capacity. You only need to focus on the implementation of application service logic, which effectively reduces O&M costs and improves the reliability and scalability of applications.
Before using CCE Autopilot, you need to purchase a cluster. You can connect to, upgrade, delete, and monitor a cluster, and manage cluster permissions.
Regions: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, CN Southwest-Guiyang1, CN South-Guangzhou-InvitationOnly, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, AF-Johannesburg, TR-Istanbul, and ME-Riyadh
-
-
Workloads
A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run them in a group of Kubernetes pods. A workload is an abstract model of a group of pods in Kubernetes. CCE Autopilot supports multiple types of workloads, including Deployments, StatefulSets, Jobs, and CronJobs.
CCE Autopilot provides native Kubernetes capabilities for you to deploy and manage containers throughout their lifecycle, such as creation, configuration, monitoring, auto scaling, upgrade, uninstallation, service discovery, and load balancing.
-
Available in all regions
-
-
Image Cache
When creating a workload, you need to pull specified container images. The image download speed affects the workload creation efficiency. To speed up workload creation, CCE Autopilot support image caches. With image caches, you can create image snapshots for the required images and create workloads using the image snapshots. This accelerates image download and workload startup. In addition, image caches reduce bandwidth consumption and prevent workload creation failures caused by network problems, improving cluster efficiency and reliability.
-
Available in all regions
-
-
Container Network
-
CCE Autopilot supports Cloud Native Network 2.0, which is a next-generation container network developed by Huawei. It allows elastic network interfaces and supplementary network interfaces to be bound to pods directly. In this way, each pod in a VPC has an independent IP address. Cloud Native Network 2.0 has higher security and reliability. With Cloud Native Network 2.0, pods can be accessed directly, security groups can be associated with pods, and EIPs can be bound to pods for internet access. In addition, compared with the container tunnel network and VPC network, Cloud Native Network 2.0 does not require container tunnel encapsulation and NAT, and provides higher network performance.
CCE Autopilot provides the following ways for accessing applications: ClusterIP Service (access within a cluster), LoadBalancer Service (load balancing), Headless Service (access between pods), Ingress (load balancing at Layer 7), and EIP.
Available in all regions
-
-
Container Storage
-
Container storage is implemented based on the Kubernetes Container Storage Interface (CSI). It is deeply integrated with Huawei Cloud storage services and fully compatible with native Kubernetes storage types.
CCE Autopilot can work with EVS, OBS, and SFS for persistent data storage. It also supports Kubernetes built-in storage types, such as emptyDir, secrets, and ConfigMaps.
Regions where EVS is available: CN North-Beijing4, CN East-Shanghai1, CN Southwest-Guiyang1, and CN South-Guangzhou-InvitationOnly
Regions where OBS is available: All regions
Regions where SFS is available: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, and CN South-Guangzhou-InvitationOnly
Regions where SFS Turbo is available: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, CN South-Guangzhou-InvitationOnly, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, AF-Johannesburg, TR-Istanbul, and ME-Riyadh
-
-
Auto Scaling
-
CCE Autopilot supports auto scaling of workloads in seconds. Multiple scaling policies can be flexibly combined to handle traffic bursts during peak hours. There are two types of policies for workload scaling: HPA policies and CronHPA policies.
- HPA policies implement horizontal scaling of pods in Kubernetes. In an HPA policy, you can configure cooldown interval and scaling thresholds based on the Kubernetes HPA.
- CronHPA can scale in or out pods in a cluster at a fixed time. It can work with HPA policies to periodically adjust the HPA scaling scope for workload scaling in complex scenarios.
Available in all regions
-
-
Container O&M
-
CCE Autopilot clusters allow you to configure log policies for collecting, managing, and analyzing workload logs periodically to prevent logs from being over-sized. In addition, CCE Autopilot clusters allow you to use the Cloud Native Log Collection add-on (log-agent) to collect logs.
CCE Autopilot can comprehensively monitor the resource usages and statuses, and network traffic of workloads. CCE Autopilot displays metrics using graphs from different dimensions for association analysis.
CCE Autopilot supports metric and event alarms. You can quickly search for and configure alarms in Alarm Center.
Available in all regions
-
-
Helm Charts
-
CCE Autopilot allows you to use Helm charts to manage and schedule resources based on the Kubernetes Helm standard, simplifying the installation and management of Kubernetes resources through quick deployment and maintenance. Those who release applications can use Helm charts to package applications, manage application dependencies and application versions, and release applications to the software repository.
By using Helm charts, you do not need to compile complex application deployment files. You can easily search for, install, upgrade, roll back, and uninstall applications.
Available in all regions
-
-
Add-ons
-
CCE Autopilot provides multiple types of add-ons to extend cluster functions.
Available in all regions
-
-
Permissions
-
CCE Autopilot permissions management allows you to assign permissions to IAM users and user groups under your tenant accounts. It combines the advantages of IAM and RBAC to provide a variety of authorization methods, including IAM fine-grained/token authorization and cluster-/namespace-scoped authorization.
Available in all regions
-
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