Inter-Actief/Beheer_Issues

Configure persistent volume for AlertManager

Open

#134 opened on Apr 14, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees) (0 forks)auto 404
good first issuekubernetes

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

Our alertmanager deployment doesn't have a persistent volume configured, so things like Silences are all wiped after the container restarts for any reason. We should add a volume to it so we can have persistent silences ;)

The configuration for our monitoring stack is in the general cluster configuration repository: https://gitlab.ia.utwente.nl/Beheer/glomgold-kubernetes-config/-/tree/main/kube-monitoring

We use the kube-prometheus-stack helm chart which also includes alertmanager as a component.

Contributor guide

Research direction
Study the kube prometheus stack Helm chart documentation to understand how to enable persistent storage for AlertManager. Look for values such as alertmanager.persistentVolumeClaim.enabled in the chart's values.yaml. Configure a PersistentVolumeClaim in your monitoring Helm values file, specifying storage class, size, and access modes. Then apply the changes via Helm upgrade.
Tech stack
kubernetes
Domain
infrastructuredevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesHelmYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60