Try It Out
In this example we will deploy Alertmanager on a Kubernetes cluster using the Minimus Prometheus Alertmanager Helm chart. Alertmanager will handle deduplication, grouping, and routing of alerts from Prometheus and other monitoring systems.
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Create Namespace
Create a namespace:
kubectl create ns prometheus-alertmanager
Step 3: Deploy the Helm Chart
Deploy the Minimus Helm chart:
helm install my-prometheus-alertmanager oci://helm.mini.dev/prometheus-alertmanager \
--version 1.40.0 \
-n prometheus-alertmanager \
--wait
If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:
helm install my-prometheus-alertmanager oci://helm.mini.dev/prometheus-alertmanager \
--version 1.40.0 \
-f values.yaml \
-n prometheus-alertmanager \
--wait
Step 4: Verify Prometheus Alertmanager is Running
Confirm the chart deployed successfully and Alertmanager started:
kubectl get pods -n prometheus-alertmanager -l app.kubernetes.io/name=alertmanager
You should see output similar to:
NAME READY STATUS RESTARTS AGE
my-prometheus-alertmanager-0 1/1 Running 0 2m
Step 5: Test HTTP Endpoint
Port-forward to the Alertmanager service and verify it responds:
kubectl port-forward svc/my-prometheus-alertmanager -n prometheus-alertmanager 9093:9093
In a separate terminal, test the health endpoint:
curl -sf http://localhost:9093/-/healthy && echo "Alertmanager is healthy"
You should see:
You can also check the Alertmanager API status:
curl -sf http://localhost:9093/api/v2/status | jq .cluster.status
Expected output:
Step 6: Clean Up
Uninstall the chart and delete the namespace to remove all resources:
helm uninstall my-prometheus-alertmanager -n prometheus-alertmanager
kubectl delete namespace prometheus-alertmanager
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.