Help Center/ Cloud Container Engine/ FAQs/ Workload/ Workload Abnormalities/ What Should I Do If a Workload Is Stopped Caused by Pod Deletion?

Updated on 2024-07-04 GMT+08:00

View PDF

What Should I Do If a Workload Is Stopped Caused by Pod Deletion?

Problem

A workload is in Stopped state.

Cause:

The metadata.enable field in the YAML file of the workload is false. As a result, the pod of the workload is deleted and the workload is in the stopped status.

Click to enlarge

Solution

Delete the enable field or set it to true.

Parent Topic: Workload Abnormalities

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.

Chatbot