Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1915403

Summary:	OCP 4.6 docs missing on how to properly setup pipeline with git secret
Product:	OpenShift Container Platform	Reporter:	peter ducai <pducai>
Component:	Documentation	Assignee:	Petr Kovar <pkovar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:	Petr Kovar <pkovar>
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, kjeeyar, ksathe, nikthoma, pchandra
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-20 14:38:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description peter ducai 2021-01-12 15:34:26 UTC

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

Comment 2 Nikhil Thomas 2021-06-01 06:52:18 UTC

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

Comment 3 Karthik Jeeyar 2021-06-01 09:01:57 UTC

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

Comment 6 Petr Kovar 2022-06-20 14:38:56 UTC

Resolved in https://issues.redhat.com/browse/RHDEVDOCS-2815.