Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release-v0.56.x] Allow imagePullBackOff for the specified duration #7678

Merged
merged 1 commit into from
Feb 26, 2024
Merged

[release-v0.56.x] Allow imagePullBackOff for the specified duration #7678

merged 1 commit into from
Feb 26, 2024

Commits on Feb 15, 2024

  1. wait for a given duration in case of imagePullBackOff 

    We have implemented imagePullBackOff as fail fast. The issue with this approach
is, the node where the pod is scheduled often experiences registry rate limit.
The image pull failure because of the rate limit returns the same warning
(reason: Failed and message: ImagePullBackOff). The pod can potentially recover
after waiting for enough time until the cap is expired. Kubernetes can then
successfully pull the image and bring the pod up.

Introducing a default configuration to specify cluster level timeout to allow
the imagePullBackOff to retry for a given duration. Once that duration has
passed, return a permanent failure.

tektoncd#5987
tektoncd#7184

Signed-off-by: Priti Desai <[email protected]>

wait for a given duration in case of imagePullBackOff

Signed-off-by: Priti Desai <[email protected]>
    @pritidesai
    pritidesai authored and tekton-robot committed Feb 15, 2024
    Configuration menu
    Copy the full SHA
    50adc45 View commit details
    Browse the repository at this point in the history