How to bind secrets to 'pipeline' service account shipped by pipeline operator

[bilalbokharee]

I am trying to extend the service account "pipeline", managed by tektonConfig, by adding authentication secrets for docker that are consumed by pipeline tasks. Is it possible to achieve this?

kind: ServiceAccount
apiVersion: v1
metadata:
  name: pipeline
  namespace: <my-namespace>
secrets:
  - name: pipeline-token-47qcr
  - name: pipeline-dockercfg-vrt2h
imagePullSecrets:
  - name: pipeline-dockercfg-vrt2h

Here, under secrets: I want to add a couple more secrets. Is this achievable?

[lebrisg]

I asked a similar but slightly more extensive question in October 2022 (#1105) without any answer until now.
However, I can answer your question based on the OpenShift documentation (https://docs.openshift.com/container-platform/4.11/cicd/pipelines/using-tekton-chains-for-openshift-pipelines-supply-chain-security.html):
"If you patch the default pipeline service account that Red Hat OpenShift Pipelines assigns to all task runs, the Red Hat OpenShift Pipelines Operator will override the service account."
To my knowledge, patching is the only way to perform what you ask for. As it's not permitted, you've got your answer.

[vdemeester]

Note that this will be fixed in the most recent version of the operator.