Help Center/ Cloud Container Engine/ User Guide/ Clusters/ Upgrading a Cluster/ Troubleshooting for Pre-upgrade Check Exceptions/ containerd Pod Restart Risks

Updated on 2024-11-12 GMT+08:00

View PDF

containerd Pod Restart Risks

Check Items

Check whether the service pods running on a containerd node are restarted when containerd is upgraded.

Solution

containerd on your node may need to be restarted. To minimize the impact on service containers, upgrade the cluster during controllable times, such as off-peak hours.

If you need help, submit a service ticket to contact O&M personnel.

Parent Topic: Troubleshooting for Pre-upgrade Check Exceptions

Previous topic: Upgrade of Cloud Native Cluster Monitoring

Next topic: Key GPU Add-on Parameters

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.