Help Center/ Cloud Container Engine/ FAQs/ Node Pool/ What Should I Do If Some Kubernetes Events Fail to Display After Nodes Were Added to or Deleted from a Node Pool in Batches?

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

View PDF

What Should I Do If Some Kubernetes Events Fail to Display After Nodes Were Added to or Deleted from a Node Pool in Batches?

Symptom

After nodes were scaled in or out in a node pool in batches, some Kubernetes events failed to display.

For instance, if 10 nodes were deleted from a cluster in batches, 10 Delete node events are printed by CCE, while only 4 StartScaleDownEmpty Kubernetes events were printed.

Click to enlarge

Possible Causes

Kubernetes limits, aggregates, and counts events before printing to ensure the availability of etcd. Therefore, Kubernetes events are not fully printed, particularly when there are numerous identical events being printed.

This is achieved through the EventCorrelate method in Kubernetes source code. For details, see design proposal in GitHub.

You do not need to pay attention to this problem, as it is caused by the Kubernetes design mechanism.

Parent Topic: Node Pool

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