Insufficient memory

default     32s         Warning   FailedScheduling        pod/elasticsearch-master-0                                          0/2 nodes are available: 2 Insufficient cpu, 2 Insufficient memory.

11m         Warning   FailedScheduling       pod/you-app                   0/28 nodes are available: 1 Insufficient memory, 1 node(s) had untolerated taint(s), 1 node(s) were unschedulable, 26 Insufficient cpu. no new claims to deallocate, preemption: 0/28 nodes are available: 2 Preemption is not helpful for scheduling, 26 No preemption victims found for incoming pod.

Related

• Insufficient cpu
• kubectl get events --sort-by='.lastTimestamp' | grep -iE "OOM|evict|kill|memory"

See also

• FailedScheduling: Insufficient cpu, Insufficient memory, timed out waiting for the condition, unbound immediate PersistentVolumeClaims, preemption, had untolerated taint(s)
• OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s), systemd-oomd, OOMKilled, oom-killer, memcpy, sar -r, Exit code: 137, Killed process, oom_reaper, oom_score_adj
• K8s troubleshooting: kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness, Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason, FailedScheduling, errImagePull, ImagePullBackOff, Kubelet conditions: MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK, CrashLoopBackOff