-
Task
-
Resolution: Done
-
Critical
-
None
-
None
-
0
-
False
-
-
False
-
Yes
-
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:
- snooze an alert
- delete the pod
- confirm that the snoozed alert is still snoozed
DONE
- mount alertmanager.yaml onto 1Mi PV
- causes
-
MGDAPI-4323 Grafana gateway error post upgrade
-
- Closed
-
- is triggering
-
MGDSTRM-9126 Name change to PVC for prometheus results in duplicates on upgrade
-
- Closed
-
- mentioned on