Feature request
Introduce a configurable grace period for TaskRun pods to be in ImagePullBackOff without failing the TaskRun.
Use case
We are using Tekton to execute TaskRuns. In our use case images for TaskRun pods cannot be pulled directly because container registry credentials must not exist in the namespace for security reasons. Instead, there’s another component in the cluster that pulls images for TaskRun pods. In case of delays in image pulling a TaskRun’s pod may be subject to ImagePullBackOff and recovers after the image has been provisioned on the respective node.
With PR #4921 (fail TaskRuns on ImagePullBackOff) we now see sporadically failing TaskRuns.
We propose to introduce a configurable grace period where ImagePullBackOff is tolerated and does not fail a TaskRun.
Feature request
Introduce a configurable grace period for TaskRun pods to be in ImagePullBackOff without failing the TaskRun.
Use case
We are using Tekton to execute TaskRuns. In our use case images for TaskRun pods cannot be pulled directly because container registry credentials must not exist in the namespace for security reasons. Instead, there’s another component in the cluster that pulls images for TaskRun pods. In case of delays in image pulling a TaskRun’s pod may be subject to ImagePullBackOff and recovers after the image has been provisioned on the respective node.
With PR #4921 (fail TaskRuns on ImagePullBackOff) we now see sporadically failing TaskRuns.
We propose to introduce a configurable grace period where ImagePullBackOff is tolerated and does not fail a TaskRun.