Tagged articles

OOMKill

3 articles · Page 1 of 1

May 6, 2024 · Cloud Native

Why Is My Kubernetes Pod OOMKilled Before Reaching Its Memory Limit?

A Kubernetes pod repeatedly restarted with exit code 137 despite not hitting its memory limit, revealing that node‑level memory pressure and QoS‑based eviction caused the pod to be killed, and outlining how to diagnose and prevent such OOMKill events.

KubernetesOOMKillQoS

0 likes · 9 min read

Why Is My Kubernetes Pod OOMKilled Before Reaching Its Memory Limit?

Liangxu Linux

Feb 3, 2024 · Operations

Why Does My Kubernetes Pod Get OOMKilled Before Reaching Its Memory Limit?

A pod in a Kubernetes cluster repeatedly restarted with exit code 137 despite staying well below its 6 Gi memory limit, prompting an investigation that uncovered the role of QoS classes, oom_score calculations, and node‑level memory pressure in the eviction process.

KubernetesOOMKillQoS

0 likes · 9 min read

Why Does My Kubernetes Pod Get OOMKilled Before Reaching Its Memory Limit?

MaGe Linux Operations

Jan 17, 2024 · Operations

Why Does My Kubernetes Pod Get OOMKilled Before Hitting Memory Limits?

This article explains why a Kubernetes pod can be OOMKilled and repeatedly restarted even before reaching its memory limit, detailing the role of QoS classes, oom_score calculations, and node‑memory pressure in the eviction process, and offers practical mitigation steps.

OOMKillQoSeviction

0 likes · 10 min read

Why Does My Kubernetes Pod Get OOMKilled Before Hitting Memory Limits?