The existing RAN ReduceMonitoringFootprint source CR does not successfully apply to spoke cluster deployments when ACM observability setup in the cluster, causing spoke Policies to go NonCompliant.

The reason is that setting to true the mco-disable-alerting as stated in https://issues.redhat.com/browse/CNF-13398 results in ACM removing the URL from the hub-info secret that is required by the ReduceMonitoringFootprint.yaml file. Reference CR snapshot: https://github.com/openshift-kni/telco-reference/blob/b7d92abab35ed1d11d921c18f696c353616d9cb0/telco-ran/configuration/source-crs/cluster-tuning/monitoring-configuration/ReduceMonitoringFootprint.yaml

Current workaround involves creating a policy in the hub to expose the URL as described in  https://issues.redhat.com/browse/CNF-13398      

OCP 4.20/ACM 2.14+
    

Always
    

    1. Enable ACM observability in the hub cluster
    2. Deploy a spoke cluster using GitOps ZTP using the RAN RDS source CRs, which include ReduceMonitoringFootprint CR
    2. Observe deployment progress.
    3.
    

Spoke deployment fails due to Policies being NonCompliant
    

Spoke deployment should succeed with the ReduceMonitoringFootprint CR applied when ACM observability is enabled in the hub