KubeMemoryOvercommit counts evicted pods

[perek]

We recently had the KubeMemoryOvercommit alert fire on a cluster of ours that was not overcommitted, it was firing because there were a few evicted pods that pushed it over the limit configured. Since evicted pods will never start should be ignore failed pods in this alert? If not should we possibly update the alert to mention that evicted pods are possible to cause this alert?

[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!