Description of problem: Customer has issue to setup pipeline with properly linked secret. Version-Release number of selected component (if applicable): Pipelines on OCP 4.6 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: As I didnt find any clear info on this issue in [2] I pointed customer to [1], but mentioned solution doesn't work and he get kubectl apply --filename secret.yaml serviceaccount.yaml run.yaml error: Unexpected args: [serviceaccount.yaml run.yaml] See 'kubectl apply -h' for help and examples [1] https://github.com/tektoncd/pipeline/blob/master/docs/auth.md [2] https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html-single/pipelines/index
> kubectl apply --filename secret.yaml serviceaccount.yaml run.yaml > error: Unexpected args: [serviceaccount.yaml run.yaml] > See 'kubectl apply -h' for help and examples This is a typo in the doc. It should be: kubectl apply --filename secret.yaml,serviceaccount.yaml,run.yaml I shall patch it in upstream docs. In addition, we shall improve the downstream docs as well.
While starting a pipeline through devconsole, we can add secrets under the Advanced options. Please Refer this https://docs.openshift.com/container-platform/4.6/pipelines/working-with-pipelines-using-the-developer-perspective.html#op-starting-pipelines_working-with-pipelines-using-the-developer-perspective
Resolved in https://issues.redhat.com/browse/RHDEVDOCS-2815.