[release-4.19] OCPBUGS-76531: feat(updates): enable CVO metrics access with RHOBS monitoring flag#7698
[release-4.19] OCPBUGS-76531: feat(updates): enable CVO metrics access with RHOBS monitoring flag#7698gaol wants to merge 3 commits intoopenshift:release-4.19from
Conversation
When --rhobs-monitoring=true is set (for ROSA HCP), enable CVO access to RHOBS Prometheus for conditional update risk evaluation. Add --cvo-prometheus-url flag to allow overriding the default Prometheus endpoint. This provides flexibility for future changes (e.g., if ROSA changes the service name) or for platforms with different monitoring architectures (e.g., ARO HCP's self-managed Prometheus). When not specified, platform-appropriate defaults are used. The CVO deployment logic routes to different metrics endpoints based on the monitoring stack: - RHOBS stack (ROSA HCP): http://hypershift-monitoring-stack-prometheus.openshift-observability-operator.svc:9090 - CoreOS stack (Self-managed HyperShift on OpenShift): https://thanos-querier.openshift-monitoring.svc:9092 For RHOBS (ROSA HCP), we always pass --metrics-ca-bundle-file and --metrics-token-file from the service account. CVO only uses these files if they exist, so passing them is safe even for HTTP endpoints that don't require TLS or authentication. This approach allows switching to a TLS-authenticated endpoint in the future by just changing the URL, without requiring code changes. Key changes: - CVO deployment enables metrics access when either --rhobs-monitoring (for ROSA HCP) or --enable-cvo-management-cluster-metrics-access (for self-managed HyperShift on OpenShift) is set - Add --cvo-prometheus-url flag to configure CVO Prometheus endpoint - Network policies updated to allow egress to the appropriate monitoring endpoint based on stack configuration
… monitoring is enabled on rosa
|
@gaol: This pull request references Jira Issue OCPBUGS-76531, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gaol The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest-required |
1 similar comment
|
/retest-required |
…ometheusURL specified
|
/retest-required |
|
@gaol: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/test verify |
What this PR does / why we need it:
release-4.19branch.hypershift-operator/controllers/hostedcluster/hostedcluster_controller.goto append the rule to thecontrol-plane-operatorrole which was done incontrol-plane-operator/controllers/hostedcontrolplane/v2/controlplaneoperator/role.goin upstream pr.Which issue(s) this PR fixes:
Fixes https://issues.redhat.com//browse/OCPBUGS-76531
Special notes for your reviewer:
Checklist: