[resolvers: bundle] Cache resolved bundle to not fetch it all the time

[vdemeester]

Feature request

Provide an option, on the bundle resolver, to be able to cache/store the resolved bundle in order to not have to fetch it each time.

• If the bundle is identified by the digest, we can cache it directly.
• If the bundle is identified by a Tag, we could query the registry if the digest we stored for this bundle is still the one targeted by the tag — if not, we re-fetch the bundle, if yes, we just use the cache.
• This could be optional.
• We would need to make the "storage" extensible (aka in emptydir, in PVC, in CSI, in s3, …)

Use case

• Reduce the number of "pull" from registries. For a PipelineRun with 10 tasks, all using the same bundle, I think we pull the bundle 10 times.
• Reduce the possible impact of service outage / flakyness. If a registry is having an outage or is flaky, as long as the bundle is already in the cache, Pipelines and Tasks wouldn't be affected.

[vdemeester]

cc @abayer

[vdemeester]

Slightly related to #6385 as well 👼🏼

[liangyuanpeng]

Slightly related to #6385 as well 👼🏼

Maybe:

• [resolvers: bundle] Errors when pulling bundles from registries should be wrapped #6386

[tekton-robot]

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.

[vdemeester]

/lifecycle frozen
/area roadmap