-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
can't select workspace in tekton-dashbord while Creating PipelineRun #6144
Comments
PipelineRun tkn/always-to-alpha-run-1676039021477 doesn't bind Pipeline tkn/always-to-alpha's Workspaces correctly: pipeline requires workspace with name "tkn" be provided by pipelinerun |
Hi @Faraaaaaaaaaaaa, thanks for raising this. It's more of a feature request than a bug so removing that label. This is already being tracked in tektoncd/dashboard#1283 (in the Dashboard repo). For now there's no UI for selecting workspace config but you can switch to YAML mode by clicking the button in the top right of the window and enter any advanced config (including workspaces) not currently available in the UI. Closing this issue since it's not related to the Pipeline project and already tracked in the Dashboard repo. /close |
@AlanGreene: Closing this issue. In response to this:
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. |
Expected Behavior
All my pipelines work's with workspace -> secret.
Need to type workspace name and select secret as i do in openshift while creating pipelinerun.
or when creating pipelinerun by yaml:
Actual Behavior
NO place in tekton-dashbord to select or type workspace->secret
Steps to Reproduce the Problem
Additional Info
OpenShift version
4.11.0-0.okd-2022-10-28-153352
Kubernetes version
v1.24.0-2566+5157800f2a3bc3-dirty
$ tkn version
Client version: 0.26.1
Pipeline version: v20230208-d7961fc543
Triggers version: v0.22.0
Dashboard version: v0.32.0
Operator version: v0.64.0
The text was updated successfully, but these errors were encountered: