Configuring Labels and Annotations
Pod Annotations
CCE allows you to add annotations using YAML to enable some advanced pod functions. The following table describes the annotations you can add.
Function and Reference |
Annotation |
Example Value |
Description |
---|---|---|---|
kubernetes.io/ingress-bandwidth |
100M |
Indicates the ingress bandwidth of a pod. This annotation controls the rate at which a pod receives data to ensure that the pod can process external requests. |
|
kubernetes.io/egress-bandwidth |
100M |
Indicates the egress bandwidth of a pod. This annotation controls the rate at which a pod sends data to external systems. This affects the efficiency of communication between the pod and external services or users. |
|
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 use workload annotations to implement AZ affinity and schedule pods to specified AZs. |
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