I mean this code - https://github.com/jenkinsci/kubernetes-plugin/blob/e44cd177808637b163ab12bfb90c8520adfe1bc7/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pod/retention/Reaper.java#L472

As I see it, the Jenkins plugin for K8s terminates the job when it notices the "Back-off pulling image" message for the container status.

Example of error message:

Unable to pull Docker image "registry.net/project:version". Check if image tag name is spelled correctly. 

There are various reasons for this:

• Invalid image tag or registry doesn't exist
• Failed to authorize in "registry.net"
• Rate limits on "registry.net" - (it can be the reason of my issue)
• Network issues
• etc

With that in mind, I think the Jenkins plugin for Kubernetes should leverage exponential backoff retry for the image pull operation.