Query: How do people run pipelines concurrently with defined PVC workspaces?

[chabeezy]

Hi,

First of all great work on tekton, it's a great product!

I was just curious, and I've struggled to find out a way to do this. I want to be able to run multiple pipelines at once, our use case is we run a set of tests on PR's when they are created/updated. It's possible for people to be pushing to different PR's at the same time. Thus triggering pipelines to run at the same time

Currently the pipeline queues up, I imagine this is because the workspace is in use.

Just wondering if its possible to give a selection of workspaces, or something similar? As in a pipeline has workspaces x,y and z. If x and y are in use, use z?

I've read you can use templates that will be deleted if you delete the pipeline run.. however I think we need to hold onto the pipeline runs for too long for that to work for us. Can you tear them down at the end of a pipeline run?

[jerop]

Just wondering if its possible to give a selection of workspaces, or something similar? As in a pipeline has workspaces x,y and z. If x and y are in use, use z?

@chabeezy wondering if you have a selection of pre-defined workspaces only because they aren't torn down when the pipelinerun are completed...or if there are other reasons

[chabeezy]

@jerop

Yes currently we don’t tear down the pipelines after each run, as we need to preserve the logs for a while.

We don’t have lots of space either so can’t create pvc templates as we’ll soon run out, or lose logs too soon due to deleting the pipeline run.

I’ve not implemented it yet, but my plan is

• Send the logs to elasticsearch
• I can then use a template for pvc and implement the cron job that deletes pipeline runs periodically.

[jerop]

@chabeezy you may be interested in the work that @adambkaplan is doing to persist logs in tekton - https://github.com/tektoncd/community/blob/main/teps/0117-tekton-results-logs.md

[austinzhao-go]

thanks @jerop for linking my question to this discussion.

perhaps a related use case from my problem

Use Case
need a pvc to pass fetched secrets between Tasks in a PipelineRun

Expected:
pvc will be deleted upon the completion of PipelineRun as "grinding" the fetched creds   
Current:
pvc will be kept and only deleted when deleting the TaskRun/PipelineRun files

thank you @chabeezy for bringing up this FR discussion!

[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.

[tekton-robot]

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.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jerop]

/reopen
/lifecycle frozen

issue is not addressed

[tekton-robot]

@jerop: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen

issue is not addressed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pritidesai]

thanks @jerop for linking my question to this discussion.

perhaps a related use case from my problem

Use Case
need a pvc to pass fetched secrets between Tasks in a PipelineRun

Expected:
pvc will be deleted upon the completion of PipelineRun as "grinding" the fetched creds   
Current:
pvc will be kept and only deleted when deleting the TaskRun/PipelineRun files

thank you @chabeezy for bringing up this FR discussion!

@austinzhao-go I have the PoC created here - #6635 Please let me know if this works for you. Thanks!

[lbernick]

It sounds like this feature request has a few parts:

1. allowing PVCs to be deleted after pipelinerun completion: Allow PVC of completed PipelineRun to be deleted #5776
2. automatic log uploads of completed taskruns: This has been implemented in the results project
3. Automatic deletion of pipelineruns after completion: Proposed in TEP-0052 (https://github.com/tektoncd/community/blob/main/teps/0052-tekton-results-automated-run-resource-cleanup.md)
4. queueing pipelineruns: Tekton Queue. Concurrency #5835

@chabeezy are there other components I'm missing? I think we may want to close out this issue since we're tracking each of these improvements in separate issues.