1. Proposed title of this feature request

Support podMetadata for custom pod annotations in user workload monitoring    

      2. What is the nature and description of the request?

We request that the Cluster Monitoring Operator (CMO) expose support for the podMetadata field in the user workload monitoring configuration, enabling users to inject custom annotations —especially for use cases like attaching secondary network interfaces via Multus (using the annotation k8s.v1.cni.cncf.io/networks).

While this capability exists in the *upstream Prometheus Operator ((https://github.com/openshift/cluster-monitoring-operator/issues/2670)* via the podMetadata field on Prometheus, Alertmanager, and related CRDs, it is not currently supported or configurable via OpenShift's user-workload-monitoring-config ConfigMap or other CMO mechanisms.

This RFE proposes adding support for specifying podMetadata for user workload Alertmanager and Prometheus pods so that custom annotations (such as Multus CNI attachments) can be injected and used at runtime.

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

•  The customer needs to attach a secondary network interface to Alertmanager or Prometheus pods using Multus. This requires injecting the annotation k8s.v1.cni.cncf.io/networks onto the pod spec—currently not possible via CMO.

• Multi-homed networking is required for routing alert traffic through isolated or dedicated interfaces for compliance, security, or performance needs.

•  The upstream Prometheus Operator already supports podMetadata for such customization. OpenShift CMO should offer equivalent configurability.

4. List any affected packages or components.

• Cluster Monitoring Operator (CMO)

• User Workload Monitoring stack