Uploaded image for project: 'Managed Service - API'
  1. Managed Service - API
  2. MGDAPI-3855

Implement persistent volume for alert manager

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • 1.26.0
    • None
    • None
    • MGDAPI - Sprint 24, MGDAPI - Sprint 25, MGDAPI - Sprint 26, MGDAPI - Sprint 28, MGDAPI - Sprint 29

      WHAT
      The alert manager pod currently uses an ephemeral volume. During events such as node restarts, OSD/RHOAM upgrades, etc. which cause the alert-manager pod to be restarted, alerts which have been silenced are lost and have resulted in unnecessary PD incidents.

      HOW
      Mounting the alertmanager.yaml as a persistent volume would preserve the silence status when the alert manager pod is restarted. Currently the config in RHOAM is under 4K, a 1Mi volume would provide plenty of space for even the most complex alert manager config for any our products using OO.

      TESTS
      Once alertmanager.yaml has been mounted on a PV:

      1. snooze an alert
      2. delete the pod
      3. confirm that the snoozed alert is still snoozed

      DONE

      • mount alertmanager.yaml onto 1Mi PV

              vmogilev_rhmi Valery Mogilevsky
              jsarnovs@redhat.com Jesse Sarnovsky
              Kevin Chi Keen Fan Kevin Chi Keen Fan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: