Open paulfantom opened 1 year ago
Caused by overloaded node during cluster reboot. Fixed by cordoning node, removing offending pods, and uncordoning node to allow pod to start properly.
Should be prevented by implementing proper memory limits after cluster resize.
Alert KubePodNotReady firing in monitoring namespace
This is an automated issue created by the monitoring system. Please do not edit this message.
Alertmanager URL: https://alertmanager.ankhmorpork.thaum.xyz
Issue was last updated at 2024-09-02 15:05:18.111067281 +0000 UTC m=+5283.918553123.
Common Labels
Common Annotations
Alerts