Possibility to exclude namespaces from OpenShift Pipelines

In OpenShift Pipelines 1.5.2, once installed each namespace will be enabled to use OpenShift Pipelines by having the necessary serviceAccount, secret and ConfigMap created.

In large OpenShift Container Platform - Cluster these objects can utilize/obtain a lot of space in etcd and thus cause a rather extensive growth. Also not each and every namespace on an OpenShift Container Platform - Cluster may want or should have access to OpenShift Pipelines.

This is why it would be nice to have a way and either opt-in or opt-out for OpenShift Pipelines usage on per namespace level. Meaning either OpenShift Container Platform - Administrator or Project Admin should be able to configure whether specific namespace should be enabled for OpenShift Pipeline usage or not.

Whether this enabling or disabling is done via annotation, custom resource, ConfigMap or something else does not matter. Key is to have a way to enable/disable namespace for OpenShift Pipelines usage and therefore the associated objects being created.