ShepherdKing
Reputation: 41
pod got killed as soon as created by job
Pod created by job gets killed with Message:
Normal DeadlineExceeded Job was active longer than specified deadline
This is a pod running training process with Tensorflow. The weird thing is this pod is just created with no thing error in kubectl log output.
Upvotes: 1
Views: 5628
Answers (1)
Radek 'Goblin' Pieczonka
Reputation: 22922
As stated in https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#job-termination-and-cleanup you can see that DeadlineExceeded means your process run longer then the longest time it is allowed to in your spec.
Upvotes: 1
Related Questions
- Pod don't run, insufficient resources
- Command terminated with exit code 7
- Pod not starting - OCI runtime create failed: runc create failed: unable to start container process
- Kubernetes job pod completed successfully but one of the containers were not ready
- Kubernetes: Pod is not created after applying deployment
- Kubernetes job keeps spinning up pods which end up with the 'Error' status
- Pod terminated with reason Error and Exit Code: 1
- Failed to "Start Container" while creating pod and gettting CrashLoopBackOff
- Tensorflow serving OOMKilled or Evicted pod with Kubernetes
- Failure to create a job in kubernetes due to error