- 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.
Pod Configuration
Check Items
Check whether the pod configuration has compatibility restrictions.
Solution
Scenario: In clusters earlier than v1.28.6-r0 or v1.27.8-r0, if the preset resource.cce.io/extra-ephemeral-storage-in-GiB annotation exists, pods may fail to be created or there may be unexpected expenses after the cluster upgrade.
The error log information is as follows:
some check failed in cluster upgrade: this cluster has podlist: map[pod-xxx pod-xxx] with system preset annotation list [resource.cce.io/extra-ephemeral-storage-in-GiB]
Check whether the pods listed in the log contain the resource.cce.io/extra-ephemeral-storage-in-GiB annotation. This annotation indicates the size of extra ephemeral storage capacity. For details, see Pod Annotations.
You can use either of the following methods to solve the problem:
- Upgrade the workload, delete the annotation, and check the pod configuration again on the cluster upgrade page. After the cluster is upgraded, new pods will not use extra ephemeral storage. The ephemeral storage for each pod is 30 GiB by default.
- Upgrade the workload, change resource.cce.io/extra-ephemeral-storage-in-GiB to a correct value, and skip the pod configuration check on the cluster upgrade page. After the cluster is upgraded, new pods will use extra ephemeral storage, and you will be billed for it. For details about pricing, see Billing Description.
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