Pre-upgrade Check
The system automatically checks a cluster before its upgrade. If the cluster does not meet the pre-upgrade check conditions, the upgrade cannot continue. To avoid risks, you can perform pre-upgrade check according to the check items and solutions described in this section.
No. |
Check Item |
Description |
---|---|---|
1 |
Check whether the target cluster is under upgrade management. |
|
2 |
|
|
3 |
Check whether the current HelmRelease record contains discarded Kubernetes APIs that are not supported by the target cluster version. If yes, the Helm chart may be unavailable after the upgrade. |
|
4 |
Check whether your master nodes can be accessed using SSH. |
|
5 |
Check whether there are discarded resources in the clusters. |
|
6 |
Check whether there are compatibility limitations between the current and target cce-controller-hpa add-on versions. |
|
7 |
The system scans the audit logs of the past day to check whether the user calls the deprecated APIs of the target Kubernetes version.
NOTE:
Due to the limited time range of audit logs, this check item is only an auxiliary method. APIs to be deprecated may have been used in the cluster, but their usage is not included in the audit logs of the past day. Check the API usage carefully. |
|
8 |
Check whether the certificate used by an HTTPS load balancer has been modified on ELB. |
|
9 |
Check whether the pod configuration has compatibility restrictions. |
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