#3686 [Feature] Better error message when pod is OOMkilled Issue created by tekumara Motivation: Why do you think this is important? When a pod is OOMKilled all I see in the UI is:

[1/1] currentAttempt done. Last Error: USER::

Goal: What should the final outcome look like, ideally? A error message that explains the pod was OOMKilled Propose: Link/Inline OR Additional context

❯ kubectl get pods
NAME                              READY   STATUS      RESTARTS   AGE
ffc6b601ca7bb04acb911-n0-0         0/1     Completed   0          126m
fc6b601ca7bb04acb911-n0-0-dn0-0   0/1     OOMKilled   0          126m

Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte