What is the nature and description of the request?

Client want to use a global mechanism to authenticate multiple Repositories in multiple Namespaces.

Why does the customer need this? (List the business requirements here)

Client want to develop a Self Service where their platform customers can order a Tekton Build (Pipelines as code) in a specific Namespace. All they have to do is to set a list of Bitbucket Repository URLs during the process of ordering a Project/Namespaces on OpenShift (Web App). In the background we create the appropriate CR Repositories in this Namespace for them. Instead of force them to deliver a SSH private key for accessing their Bitbucket Repositories we want to offer them our SSH public key which they can deposit on their Repositorie(s). For this we need a "global" mechanism for the operator to authenticate multiple Repositories in multiple Namespaces with the same SSH private key.

How would the customer like to achieve this? (List the functional requirements here)

A way (probably a secret in the operator Namespaces openshift-pipelines) with which the Pipelines as code Controller can authenticate multiple Repositories in multiple Namespaces on the cluster.

For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Use a secret with which the Pipelines as code Controller can authenticate multiple Repositories in multiple Namespaces. Right now it seems to be necessary that the Auth Secret and the CR Repository have to be in the same Namespace.