You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Configurable grace period for TaskRun pods in ImagePullBackOff #5987
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.
@rinckm thank you for sharing your use case for this feature request; we had discussed supporting this as future work for TEP-0092 -- the TEP has not been implemented yet, we welcome contributions in implementing it
Hello @shuheiktgw, thank you for offering to implement this, that would be great.
The TEP already exists and is in an implementable state. @jerop@bobcatfish@Aleromerog FYI
Sure, I'm happy to collaborate🙂 Hi @EmmaMunley, how is the implementation going so far? I'd appreciate it if you would push any WIP changes so that I can see if there is anything I can help!
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
Activity
jerop commentedon Jan 12, 2023
@rinckm thank you for sharing your use case for this feature request; we had discussed supporting this as future work for TEP-0092 -- the TEP has not been implemented yet, we welcome contributions in implementing it
cc @bobcatfish @Aleromerog
/help-wanted
shuheiktgw commentedon Jan 22, 2023
Hi, may I try implementing the TEP-0092? 👋
/assign
afrittoli commentedon Jan 24, 2023
Hello @shuheiktgw, thank you for offering to implement this, that would be great.
The TEP already exists and is in an implementable state.
@jerop @bobcatfish @Aleromerog FYI
jerop commentedon Jan 24, 2023
@shuheiktgw thank you for offering to implement -- @EmmaMunley has also started looking into implementing TEP-0092, maybe you can collaborate?
shuheiktgw commentedon Jan 24, 2023
Sure, I'm happy to collaborate🙂 Hi @EmmaMunley, how is the implementation going so far? I'd appreciate it if you would push any WIP changes so that I can see if there is anything I can help!
EmmaMunley commentedon Jan 25, 2023
Hi @shuheiktgw! Sure! I am working on implementing the scheduling timeout feature first as part of this issue: #4078.
tekton-robot commentedon Apr 25, 2023
Issues go stale after 90d of inactivity.
Mark the issue as fresh with
/remove-lifecycle stalewith a justification.Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with
/closewith a justification.If this issue should be exempted, mark the issue as frozen with
/lifecycle frozenwith a justification./lifecycle stale
Send feedback to tektoncd/plumbing.
tekton-robot commentedon May 25, 2023
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with
/remove-lifecycle rottenwith a justification.Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with
/closewith a justification.If this issue should be exempted, mark the issue as frozen with
/lifecycle frozenwith a justification./lifecycle rotten
Send feedback to tektoncd/plumbing.
10 remaining items
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
wait for a given duration in case of imagePullBackOff
vdemeester commentedon Jul 1, 2024
Given that #7666 is merged (see docs), I'll go ahead and close this.