Service monitors deployed by tektonInstallerSets have incorrect monitoring namespace

[mustafaStakater]

Expected Behavior

ServiceMonitor (monitoring.coreos.com/v1) installed in target namespace by TektonInstallerSets should have monitoringNamespace = targetNamespace.

Actual Behavior

The monitoring namespace in service monitor is openshift-pipelines rather than the target namespace specified in tektonConfig.

Steps to Reproduce the Problem

1. Install the openshift-pipelines operator. Disable the default tektonconfig with AUTOINSTALL_COMPONENTS set to false
2. Create the tektonconfig custom resource with targetNamespace set (different from openshift-pipelines)
3. View the servicemonitors deployed in target namespace.

Screenshot

Additional Info

• OpenShift version: 4.11.42
• Kubernetes version: v1.24.12+ceaf338
• Openshift Pipelines Operator version: v1.10.4
• Tekton Pipelines version: v0.44.2

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.