KubeMemoryOvercommit (and family) does not cordoning nodes into consideration

[mladedav]

We had a cluster where someone cordoned a few nodes and we have found out only when a node was restarted. I think that this should be part of the alert because a node failure may cause the cluster to be unable to schedule all pods.

[github-actions]

This issue has not had any activity in the past 30 days, so the
stale label has been added to it.

• The stale label will be removed if there is new activity
• The issue will be closed in 7 days if there is no new activity
• Add the keepalive label to exempt this issue from the stale check action

Thank you for your contributions!

[skl]

Seems like a genuine concern, not sure if KubeMemoryOvercommit is the right alert for this but some alert which says "cluster is unable to schedule all pods" sounds useful.