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.
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.
Node Pool FAQs
- What Should I Do If a Node Pool Is Abnormal?
- What Should I Do If No Node Creation Record Is Displayed When the Node Pool Is Being Expanding?
- What Should I Do If a Node Pool Scale-Out Fails?
- What Should I Do If Some Kubernetes Events Fail to Display After Nodes Were Added to or Deleted from a Node Pool in Batches?
- How Do I Modify ECS Configurations When an ECS Cannot Be Managed by a Node Pool?
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.
Chatbotmore
