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

Workspace default to empty Dir #4173

Closed
hakuna-matatah opened this issue Aug 18, 2021 · 3 comments
Closed

Workspace default to empty Dir #4173

hakuna-matatah opened this issue Aug 18, 2021 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@hakuna-matatah
Copy link

Feature request

Today we need to define workspace as part of triggertemplate or Task or pipeline:

      workspaces:
      - name: source
        emptyDir: {}
      - name: config
        emptyDir: {}
      - name: results
        emptyDir: {}

Use case

Could we have it defaulted to emptyDir when nothing is specified ?

@hakuna-matatah hakuna-matatah added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 18, 2021
@ghost
Copy link

ghost commented Aug 19, 2021

Bringing over my comment from Slack:

You can configure emptyDir to be the default for taskruns today. We don't have a general approach like this for pipelineruns tho.

Edit the config-defaults configmap in your tekton-pipelines namespace and set the default-task-run-workspace-binding to be the workspace binding you want (e.g. emptyDir: {})

Example: https://github.com/tektoncd/pipeline/blob/main/config/config-defaults.yaml#L66-L70

@ghost
Copy link

ghost commented Aug 19, 2021

Also I just realised we do already have a feature ticket for this.

Closing as a duplicate of #2595

@ghost ghost closed this as completed Aug 19, 2021
@hakuna-matatah
Copy link
Author

Thanks for the details. I'm looking for something in pipelineruns. This ticket would help - #2595

This issue was closed.
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