I am triggering pipelineRun via triggerTemplate and the volume is used for cloning a github repository and doing some jobs in it. I want to use volumeClaim and delete it after pipelineRun finishes.
Is there any other way to delete pvc after pipelinerun??
If not, then what is the best practice to build docker image and deploy in tekton pipelines?
Thanks in advance!
GwonsooLee
All 13 comments
It is easiest to delete the PipelineRun - then the PVC created by volumeClaimTemplate is also deleted.
jlpettersson
on 25 Jun 2020
/kind feature
The suggestion by @jlpettersson is likely the best short term answer.
@sbwsg Any thoughts on if/how we will do automatic volume cleanup for volumeClaimTemplates?
wlynch
on 26 Jun 2020
Thanks for answering. @jlpettersson @wlynch
We actually considered deleting pipelineRun.. But if I wanted to keep the build/deploy log, I think I have to store them to other place like s3 or elasticsearch, etc, don't I?
We are trying to keep all logs of pipelineRuns at least a week... Actually I changed to use NFS not to create pvc every time for every build. This is kind of a temporary solution for us (We just adopt to use tekton for CI/CD pipeline).
@wlynch If deleting pipelineRuns when completed is the best short term solution, then, is it common to store pod logs to somewhere?? I am just wondering what is the best practice (if exists) of tekton pipeline~ I want to use it as efficient as possible :)
GwonsooLee
on 30 Jun 2020
@GwonsooLee there is an experimental project around this (and a design doc).
vdemeester
on 30 Jun 2020
@vdemeester Thank you so much for introducing experimental project. result api seems perfect if applied. I will look it over! And, I requested access to the design doc, but not yet granted. Is there anything I have to do for getting access or just wait? I just wanted to know if there is something I have to request but I didn't yet. Thanks again
GwonsooLee
on 1 Jul 2020
@vdemeester Thank you so much for introducing experimental project.
result apiseems perfect if applied. I will look it over! And, I requested access to the design doc, but not yet granted. Is there anything I have to do for getting access or just wait? I just wanted to know if there is something I have to request but I didn't yet. Thanks again
You should automatically have access to it if you are part of the tekton-dev google group, see here
vdemeester
on 1 Jul 2020
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
Send feedback to tektoncd/plumbing.
tekton-robot
on 15 Aug 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
tekton-robot
on 15 Aug 2020
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./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.
tekton-robot
on 15 Aug 2020
/remove-lifecycle rotten
/remove-lifecycle stale
/reopen
vdemeester
on 17 Aug 2020
@vdemeester: Reopened this issue.
In response to this:
/remove-lifecycle rotten
/remove-lifecycle stale
/reopen
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.
tekton-robot
on 17 Aug 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.
/lifecycle stale
Send feedback to tektoncd/plumbing.
tekton-robot
on 15 Nov 2020
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
on 15 Dec 2020
Related issues
csantanapr
·
3Comments
andydude
·
3Comments
castlemilk
·
4Comments
sbwsg
·
3Comments
vdemeester
·
3Comments
Most helpful comment
@GwonsooLee there is an
experimentalproject around this (and a design doc).