A Pending Pod has not been placed on a node. The scheduler explains why in a FailedScheduling event that counts nodes per reason, for example 0/3 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 2 Insufficient memory. Read it before you change anything.
The usual reasons: requests larger than any node's free capacity; a nodeSelector or affinity that no node's labels satisfy; taints the Pod doesn't tolerate; nodes cordoned with SchedulingDisabled; or a claim that doesn't exist or can't bind. Each has a different fix, and only some belong in the workload: sometimes the node needs a label or an uncordon.
OOMKilled is the opposite failure: the Pod ran, then the kernel killed the container for passing its memory limit. kubectl get pods shows CrashLoopBackOff; describe shows Last State OOMKilled, exit 137. Raise the limit to what the app really needs, or fix the app's memory use.
Why no node fits, what the nodes offer, and how the last run ended.