Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-1749

Expose field in CMO config to disable Alertmanager


    • False
    • False
    • NEW
    • TELCOSTRAT-87 - Single Core CPU CaaS Budget for DU Deployment w/ Single-Node OpenShift on Sapphire Rapids Platform
    • Undefined
    • Monitoring - Sprint 204, Monitoring - Sprint 205

      Use cases like single-node deployments (e.g. far-edge) don't need to deploy a local Alertmanager cluster because alerts are centralized at the core (e.g. hub cluster), running Alertmanager locally takes resources from user workloads and adds management overhead. Cluster admins should be able to not deploy Alertmanager as a day-2 operation.


      • Alertmanager isn't deployed when switched off in the CMO configmap.
      • The OCP console handles the situation gracefully when Alertmanager isn't installed informing users that it can't manage the local Alertmanager configuration and resources.
        • Silences page
        • Alertmanager config editor

            fpetkovs@redhat.com Filip Petkovski (Inactive)
            spasquie@redhat.com Simon Pasquier
            Junqi Zhao Junqi Zhao
            0 Vote for this issue
            3 Start watching this issue