It's hard to tell the exit status (exit code, OOM status) of a container when it exits due to another process deleting the pod.

This was seen in a customer issue where a child process (gradle build) in a Jenkins slave pod was killed by the OOM killer, and the Jenkins master then deleted the pod before it exited naturally.

Had the pod exited naturally, the reason: OOMKilled and exit code would have been visible in the pod status.

Adding kubernetes Events for all container lifecycle events, including exit code and OOM indication would have helped customer and Red Hat to diagnose the issue faster.

https://github.com/kubernetes/kubernetes/pull/45682 would be a foundation for this work, but would need to be further extended to make the OOM indication visible.