Prometheus configuration in cluster-monitoring-config configmap is reverted in ARO

Solution Verified - Updated -

Environment

  • Azure Red Hat OpenShift (ARO)
    • 4
  • OpenShift Managed (Azure)
    • 4

Issue

  • Changes in the persistent storage or in the retention period for Prometheus done in the configmap cluster-monitoring-config are reverted in ARO.

  • Cannot add a PersistentVolume (PV) to Prometheus pod

Resolution

  • Configuring Prometheus is not supported in ARO. A custom Prometheus instance is needed to be able to manage that configuration

Root Cause

  • Configuring Prometheus is not supported in ARO as shown in the Azure Red Hat OpenShift support policy.
  • The ARO operator aro-operator-master reverts changes to the monitoring configuration back to a supported configuration. Specifically, any changes to Retention and Storage configuration will be reverted.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments