Skip to content

Configurable grace period for TaskRun pods in ImagePullBackOff #5987

Closed

Description

@rinckm

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.

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Jan 12, 2023
  2. jerop commented on Jan 12, 2023

    @jerop
    Member

    @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

  3. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Jan 12, 2023
  4. shuheiktgw commented on Jan 22, 2023

    @shuheiktgw

    Hi, may I try implementing the TEP-0092? 👋
    /assign

  5. afrittoli commented on Jan 24, 2023

    @afrittoli
    Member

    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

  6. jerop commented on Jan 24, 2023

    @jerop
    Member

    @shuheiktgw thank you for offering to implement -- @EmmaMunley has also started looking into implementing TEP-0092, maybe you can collaborate?

  7. shuheiktgw commented on Jan 24, 2023

    @shuheiktgw

    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!

  8. EmmaMunley commented on Jan 25, 2023

    @EmmaMunley
    Contributor

    Hi @shuheiktgw! Sure! I am working on implementing the scheduling timeout feature first as part of this issue: #4078.

  9. tekton-robot commented on Apr 25, 2023

    @tekton-robot
    Collaborator

    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.

    /lifecycle stale

    Send feedback to tektoncd/plumbing.

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 25, 2023
  11. tekton-robot commented on May 25, 2023

    @tekton-robot
    Collaborator

    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.

    /lifecycle rotten

    Send feedback to tektoncd/plumbing.

  12. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 25, 2023
  13. 10 remaining items

  14. vdemeester commented on Jul 1, 2024

    @vdemeester
    Member

    Given that #7666 is merged (see docs), I'll go ahead and close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址