-
Bug
-
Resolution: Done
-
Critical
-
ACM 2.6.0
-
1
-
False
-
None
-
False
-
-
-
Observability Sprint 2023-11
-
Critical
-
No
Description of problem:
The resolution/workaround for ACM-1933, OCPBUGS-1025, ACM-2949 has two aspects. We need specific configuration details for these:
- Configuration on the hub cluster to disable all writes to the monitoring configmap of the spoke clusters.
- Content which is required by Observability and now needs to be added to the configmap by the user (via Policy in our use case)
Thanks!
Version-Release number of selected component (if applicable): 2.6
How reproducible: 100%
- is cloned by
-
ACM-5623 (ACM 2.7) Configuration for Observability needed
- Closed
- relates to
-
OCPBUGS-1025 [tracker]cluster-monitoring-config race condition between Observability and du profile
- ON_QA
-
ACM-2949 Observability writing null config values to DU profile maintained configuration causes policies to show non-compliant
- Closed