Service monitors deployed by tektonInstallerSets have incorrect monitoring namespace
Open
Nobody has claimed this yet.
kind/bug
lifecycle/rotten
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
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
- Install the openshift-pipelines operator. Disable the default tektonconfig with AUTOINSTALL_COMPONENTS set to false
- Create the tektonconfig custom resource with targetNamespace set (different from openshift-pipelines)
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how TektonInstallerSets generate ServiceMonitor resources and how targetNamespace is read from tektonConfig. Reproduce the issue with a target namespace different from openshift-pipelines; done when the generated monitoringNamespace matches the target namespace and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100