According to the latest upstream version of Tekton, *it is not possible to configure a specific cloud-events-sink for PipelineRun or TaskRun *[1]. It is only possible to set this in the clusterwide config-defaults configmap in the openshift-pipelines namespace.

Usually OpenShift Pipelines is installed globally and this approach can't work in a cluster-wide installation. I also could not find an upstream issue related to this topic hence I am raising this RFE. For our usecase this is a crucial feature and the customer would love to see this implemented so that they can react on events caused by Tekton but on a case-by-case basis.

[1] https://github.com/tektoncd/pipeline/blob/adaae90b9bb93aa96cb345f75bf7797a12f8c308/config/config-defaults.yaml#L59

Feature should be used on multiple production grade clusters to facilitate continuous integration and deployment tasks. At this stage no feasible workaround is implemented. It might be possible to develop and deploy an event sink that acts as a forwarder with static routing capabilities but this situation is far from ideal and would require a lot of glue code just to make it work.

If the feature is changed in any way, then the full TLS scope must be adjustable: certificates, TLS on/off, etc. As some customers (tenants) do not have full control over this, which makes using cloud event sinks even more difficult. In our case we have some unsigned or self-signed routes that we can not adjust to our needs.