Platform & DevOps·Placement, resources and the pod lifecycle
the container went one byte over its memory ceiling and the kernel killed it outright, mid-request.
Resource limit
Also calledlimit, CPU limit, memory limit, cap
The hard ceiling a container may consume, enforced by the kernel rather than by the scheduler. The two resources behave completely differently at the ceiling: CPU is throttled, so the workload gets slow, and memory is not compressible, so the process is killed. That asymmetry is why a CPU limit shows up as mysterious latency and a memory limit shows up as a restart loop.