0
  • version

k8s 1.15

  • problem

I run a job with 2Gi memory limit which seems to be not enough. The status of the job shows "completed" with 1 succeeded pod; what strange is that the pod terminated with exitcode 0, which is known as completed successfully, but infact is was killed by out of memory.

enter image description here

rock'n rolla
  • 1,883
  • 1
  • 13
  • 19
fresh learning
  • 71
  • 7
  • Is it one time issue, or does this happen frequently? – Matt Apr 01 '21 at 11:16
  • I have encountered this several times in my impression, no more than 10 in 5 months – fresh learning Apr 01 '21 at 11:44
  • Did you ever find out why this was happening? We also had an OOMKilled container that was started by a Job. The Job responded success so it was really hard to figure out what was going on. – Andrew Aug 16 '23 at 01:06

0 Answers0