-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13.z
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-8713. The following is the description of the original issue:
—
Description of problem:
Currently, the hypershift namespace servicemonitor has the api group rhobs.com, which results in the hypershift operator metrics not being scraped by CMO. Additionally, the hypershift deployment comes with recording rules that require metrics from the CMO. The servicemonitor's apigroup needs to be changed back to `coreos.com` for the following reasons: - future observability of the hypershift operator by the CMO, as we do for other operators - functional recording rules (https://github.com/openshift/hypershift/blob/main/cmd/install/assets/recordingrules/hypershift.yaml)
Version-Release number of selected component (if applicable):
4.13.4
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
See slack thread: https://redhat-internal.slack.com/archives/C04EUL1DRHC/p1678289562185509?thread_ts=1677690924.397839&cid=C04EUL1DRHC
- clones
-
OCPBUGS-8713 Hypershift namespace servicemonitor has wrong API group
- Closed
- is blocked by
-
OCPBUGS-8713 Hypershift namespace servicemonitor has wrong API group
- Closed
- links to