tektoncd/pipeline

Retry failed resolvers

Offen

#8.571 geöffnet am 17.02.2025

 (1 Kommentar) (0 Reaktionen) (0 zugewiesene Personen)Go (1.943 Forks)auto 404
area/apiarea/resolutionhelp wantedkind/feature

Repository-Metriken

Stars
 (9.013 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 9T 3h) (137 gemergte PRs in 30 T)

Beschreibung

Feature request

While it is convenient to use resolvers to reference tasks and pipelines not present in the cluster, the resolution requests are very susceptible to reliability issues. Tekton should be able to automatically retry requests to resolve. Requests shouldn't be retried in perpetuity as this could present confusion as to why the pipeline isn't scheduling. It may be beneficial for users to configure the number of retries and/or the backoff strategy when deploying Tekton to the cluster.

Use case

As a user of Tekton bundles, I want to be able to resolve the pushed definitions even when the container registry is undergoing intermittent reliability/stability issues.

As a user of Tekton bundles, I want to be able to resolve the referenced definitions even when the git provider is undergoing intermittent reliability/stability issues.

Contributor Guide