In a customer issue it was hard to diagnose that a child process in a Jenkins slave running on OpenShift was killed by the OOM killer.  The following items would have helped:

1) Jenkins Kubernetes plugin should cleanly terminate the slave agent when it's done, rather than delete its pod.  This would enable Reason: OOMKilled to be seen on the pod status, as well as giving a chance for a meaningful exit code to be set.

2) The Jenkins Kubernetes plugin should look for Reason: OOMKilled on the pod status after slave agent exits, and clearly log if it is seen.

3) It should be possible to disable automatic pod deletion for debugging purposes, allowing slave logs to be recovered and the pod status to be investigated.