-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.z, 4.19.z
-
None
Description of problem:
When installing a 4.18 or 4.19 cluster in ROSA HCP, metrics scraping of the cluster-version-operator fails. It is failing because CVO requires bearer token based authentication of the /metrics endpoint now. I've spun this ticket out of OCPBUGS-62851, to track a new --serving-client-certificate-authorities-file CVO option that would allow HyperShift to pass the CVO a list of trusted client-signing CAs, to match the approach they already use for other ServiceMonitors.
Version-Release number of selected component
4.20, 4.19.9 and later, and 4.18.23 and later.
How reproducible
Every time
Steps to Reproduce
- Install the latest 4.18 or 4.19 cluster
- Check the openshift-observability-operator stack looking for cluster_operator_up, cluster_version, or other CVO-served metrics.
Actual results
Target scraping failing with 401s.
Expected results
Successfully-scraped CVO metrics like cluster_operator_up.
- clones
-
OCPBUGS-62851 ServiceMonitor for cluster-version-operator not working due to CVO requiring bearer token authentication
-
- POST
-
- is related to
-
OCPBUGS-62861 HyperShift ServiceMonitor for cluster-version-operator metrics: revert client auth
-
- MODIFIED
-
- links to