-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
All
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The existing RAN ReduceMonitoringFootprint source CR does not successfully apply to spoke cluster deployments when ACM observability is not setup on the hub cluster. 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 is to disable this CR on the spoke config, but this configuration doesn't comply with RAN RDS
Version-Release number of selected component (if applicable):
OCP 4.20/ACM 2.14+
How reproducible:
Always
Steps to Reproduce:
1. Deploy a spoke cluster a per the RAN RDS required source CRs, which include ReduceMonitoringFootprint CR 2. Observe deployment progress, check deployment progress / policy compliance state of spoke cluster deployment 3.
Actual results:
Spoke deployment fails due to template render failure.
Expected results:
Spoke deployment should succeed with the ReduceMonitoringFootprint CR applied, independently of whether ACM observability is enabled or not on the hub.
Additional info: