- 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
Copied.
Configuring Labels and Annotations
Pod Annotations
CCE Autopilot clusters provide multiple advanced functions during pod creation. To enable these functions, you can add annotations to pods on the console or using YAML. Table 1 describes the available annotations.
Function and Reference |
Annotation |
Example Value |
Description |
---|---|---|---|
node.cce.io/node-az-list |
cn-east-3a,cn-east-3b |
Lists the AZs for pod affinity. For a CCE Autopilot cluster, you can set workload annotations to implement AZ affinity and schedule pods to specified AZs. |
|
resource.cce.io/extra-ephemeral-storage-in-GiB |
14 |
Indicates the extra ephemeral storage capacity for a pod, in GiB. The value ranges from 0 to 994. Each pod can have 30-GiB free ephemeral storage and specified extra storage. Only clusters v1.28.6-r0, v1.27.8-r0, and later support this function. Clusters of other versions need to be upgraded to support this function. |
You can add an annotation on the console or using YAML.
Adding an Annotation on the Console
When creating a workload on the console, you can choose Advanced Settings > Labels and Annotations and add pod annotations to enable advanced functions.
For example, to add 14 GiB of ephemeral storage capacity for a pod, set Pod Annotation to resource.cce.io/extra-ephemeral-storage-in-GiB=14 and click Confirm.

Adding an Annotation Using YAML
When creating a workload using YAML, you can use the annotations parameter to enable advanced pod functions.
For example, when creating an Nginx workload, you can use annotations to add 14 GiB of ephemeral storage capacity for a pod.
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx # Workload name
spec:
replicas: 1 # Number of pods
selector:
matchLabels: # Selector for selecting resources with specific labels.
app: nginx
template:
metadata:
labels: # Labels
app: nginx
annotations:
resource.cce.io/extra-ephemeral-storage-in-GiB: '14'
spec:
containers:
- image: nginx:latest # {Image name}:{Image tag}
name: nginx
imagePullSecrets:
- name: default-secret
Pod Labels
You can use pod labels to organize, select, and manage resources for pods to make it easy to use and maintain resources.
When you create a workload on the console, the following labels are added to the pod by default. The value of app is the workload name.

Example YAML:
... spec: selector: matchLabels: app: nginx version: v1 template: metadata: labels: app: nginx version: v1 spec: ...
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