1. Proposed title of this feature request

Enable Cluster Monitoring Operator’s Thanos Query gRPC Port to Bind on All Interfaces for External Chaining
2. What is the nature and description of the request?

Currently, the Thanos Query instance deployed by the Cluster Monitoring Operator binds its gRPC port to localhost, which restricts access to local connections only. This configuration prevents chaining the CMO-managed Thanos Query to another Thanos Query instance deployed externally. The request is to allow the gRPC port to bind to 0.0.0.0 (or make the bind address configurable) so it can accept connections from other Thanos Query instances.

3. Why does the customer need this? (List the business requirements here)

The customer needs to achieve a global view of metrics by aggregating data from multiple OpenShift clusters into a central observability stack. Allowing CMO’s Thanos Query to be chained with an external Thanos Query would enable federated queries across clusters, improving observability, reducing operational complexity, and enhancing cross-cluster troubleshooting capabilities. Without this feature, multi-cluster metrics aggregation cannot be accomplished natively.

4. List any affected packages or components.

cluster-monitoring-operator

Thanos Query component managed by CMO