Help Center/ Cloud Container Engine/ User Guide (Kuala Lumpur Region)/ Clusters/ Upgrading a Cluster/ Troubleshooting for Pre-upgrade Check Exceptions/ kubelet

Updated on 2024-10-14 GMT+08:00

View PDF

kubelet

Check Items

Check whether the kubelet on the node is running properly.

Solution

Scenario 1: The kubelet status is abnormal.
If the kubelet malfunctions, the node is unavailable. Restore the node and check again. For details, see What Should I Do If a Cluster Is Available But Some Nodes Are Unavailable?
Scenario 2: The cce-pause version is incorrect.
The version of the pause container image on which kubelet depends is not cce-pause:3.1. If you continue the upgrade, pods will restart in batches. Currently, the upgrade is not supported. Contact technical support.

Parent topic: Troubleshooting for Pre-upgrade Check Exceptions

Previous topic: Node Key Directory File Permissions

Next topic: Node Memory

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.