Repository navigation
[19.0-beta] Configure MCP server Prometheus/metric-storage connection - #2192
Conversation
On RHOSO versions where metric-storage is not registered in the Keystone catalog, the observabilityclient running inside the rhos-mcps sidecar cannot auto-discover Aetos/Prometheus and metric commands fail. Detect a telemetry MetricStorage CR in the OpenStackClient's namespace during MCP reconciliation and, when found, render its connection details (host/port, and CA cert path when Prometheus TLS is enabled) into the openstack.prometheus section of the rendered MCP config.yaml. When no MetricStorage is found, the section is omitted so the MCP server can report a clear "not configured" error instead of pointing at a nonexistent host. This mirrors the approach taken in lightspeed-operator commit 57acabc40fdf3695b42abcd85110c58e908454b4, reusing the existing telemetry-operator MetricStorage watch, RBAC, and lookup already used by the OpenStackClient controller for the CLI pod's Prometheus env vars. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
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 ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
916746b
into
openstack-k8s-operators:19.0-beta
This is an automated cherry-pick of #2165
/assign lpiwowar