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.

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

Enable larger results without a sidecar on every TaskRun #8448

Open
arewm opened this issue Dec 18, 2024 · 0 comments
Open

Enable larger results without a sidecar on every TaskRun #8448

arewm opened this issue Dec 18, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@arewm
Copy link

arewm commented Dec 18, 2024

Feature request

We are trying to use Tekton Chains in order to generate provenance attestations for artifacts produced during a PipelineRun. Use of type hinting means that we need to output the image URI in results so that Chains can find it. While this approach works fine when there are a small number of artifacts produced in a TaskRun, it quickly becomes insufficient as the length of a digest-pinned OCI reference, for example, will quickly consume the available space for results, especially if a task has multiple steps.

One of the main recourses that we have considered is to start using sidecar containers to increase the space available for results, but this will result in a larger consumption for every TaskRun whether it needs additional result space or not. Since I know which tasks are likely to overflow the space available for results, I would like to be able to selectively increase the result size limit to be a more responsible cluster tenant.

Use case

  • As a Task developer, I want to selectively increase the size available for my results.
  • As a Task developer, I want to be able to easily create a new task that will result in many artifacts being signed by Chains.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant