Determining that a Job failure was due to image pull errors in Kubernetes
When creating a kubernetes Job, it can fail for several different reasons, one of which is that the associated container image cannot be successfully pulled from the registry. However, after the job has completed I can’t figure out a way to definitively determine that the failure was due to an image pull failure rather than some other err that caused the deadline to be exceeded.