1. Proposed title of this feature request

Enable user-defined node placement for openshift-monitoring components in OpenShift HCP environments.

Motivation:

In traditional self-managed OpenShift clusters, it is a best practice to isolate observability workloads (e.g., Prometheus, Alertmanager, Telemetry) on dedicated infra nodes. This approach ensures:

• Better stability and predictability of metrics ingestion.
• No resource contention with business applications.
• Independent observability scaling based on monitoring needs.

Currently in HCP, even though users can define multiple nodepools, all openshift-monitoring workloads are scheduled on customer-managed worker nodes by default. There is no supported way to configure this behavior via cluster-monitoring-config.

Request:

• Official support for setting custom tolerations, nodeSelector, or affinity rules for openshift-monitoring components in HCP.
• Support for editing cluster-monitoring-config in HCP to enable this configuration in a documented and supported way.

Expected Benefits:

• Improved observability by reducing interference from other workloads.
• Alignment of HCP with best practices from self-managed clusters.
• Greater operational flexibility for platform teams.
• A more enterprise-ready HCP experience for customers with strict monitoring requirements.

The RFE has been requested by Telefonica Cybersecurity & Cloud Tech SL (7148461)