At present, the OpenShift specific changes (eg: adding service monitor resource) is handled by editing the "release.yaml" generated in midstream. This creates a hard and inconvinient dependency on midstream releases of components. eg: openshift/tektoncd-pipeline and openshift/tektoncd-triggers release has to happen before we can make a operator release for OpenShift, even if the respective upstream releases have already available.

We can move the "editing the yaml" part to the operator code so that, operator can handle the OpenShift specific changes in code.

Acceptance Criteria

• OpenShift builds of tektocd/operator performs all customizations to payloads (pipeline, triggers release.yaml) in code
• There is no dependency for operator on midstream releases, except for images.