Platform & DevOps·Placement, resources and the pod lifecycle
the container has no stack trace and no error log, just a restart count going up and exit code 137.
OOM kill
Also calledout of memory kill, OOMKilled, exit code 137
The kernel terminating a process that exceeded its memory cgroup limit, with no chance for the application to react. It is silent from inside the container by design, which is why the symptom is a gap in the logs rather than an exception. Distinguishing an application memory leak from a limit set below the workload's genuine working set is the whole of the diagnosis, and only the trend across restarts tells you which.