\n\n# Prometheus Alertmanager Helm Chart\n\nThe Alertmanager handles alerts sent by client applications such as the Prometheus server. The Prometheus Alertmanager Helm chart automates deployment and configuration of Alertmanager in Kubernetes clusters using Minimus images.\n\n\n## {{icon-list-search}} Prerequisites\n\n- A subscription to the Minimus images included in the chart\n- A running Kubernetes cluster (v1.25 or higher is recommended)\n- `kubectl` installed and configured\n- Helm v3.8 or higher for OCI support ([Installation instructions](https://helm.sh/docs/intro/install/))\n- Cluster Admin privileges\n- Persistent storage available in your cluster\n\n

\n\n---\n\n

\n\n## {{icon-rocket}}Try It Out\n\nIn 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.\n\n

\n\n### Step 1: Start Cluster\n\n

\n\nIf you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. [Deployment instructions](https://minikube.sigs.k8s.io/docs/start/?arch=%2Flinux%2Fx86-64%2Fstable%2Fbinary+download)\n\n

\n\n### Step 2: Create Namespace\n\n

\n\nCreate a namespace:\n\n```\nkubectl create ns prometheus-alertmanager\n```\n\n{{if-enterprise}}\n\nNext, create a Kubernetes secret for the Minimus token:\n\n```\nkubectl create secret docker-registry minimus-registry \\\n --docker-server=reg.mini.dev \\\n --docker-username=minimus \\\n --docker-password={{pull-token}} \\\n --namespace=prometheus-alertmanager\n```\n\n{{/if-enterprise}}\n\n

\n\n### Step 3: Deploy the Helm Chart\n\n

\n\nDeploy the Minimus Helm chart:\n\n```\nhelm install my-prometheus-alertmanager {{oci-url}} \\\n --version {{chart-version}} \\\n -n prometheus-alertmanager \\\n --wait\n```\n\nIf 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`:\n\n```\nhelm install my-prometheus-alertmanager {{oci-url}} \\\n --version {{chart-version}} \\\n -f values.yaml \\\n -n prometheus-alertmanager \\\n --wait\n```\n\n

\n\n### Step 4: Verify Prometheus Alertmanager is Running\n\n

\n\nConfirm the chart deployed successfully and Alertmanager started:\n\n```\nkubectl get pods -n prometheus-alertmanager -l app.kubernetes.io/name=alertmanager\n```\n\nYou should see output similar to:\n\n```\nNAME READY STATUS RESTARTS AGE\nmy-prometheus-alertmanager-0 1/1 Running 0 2m\n```\n\n

\n\n### Step 5: Test HTTP Endpoint\n\n

\n\nPort-forward to the Alertmanager service and verify it responds:\n\n```\nkubectl port-forward svc/my-prometheus-alertmanager -n prometheus-alertmanager 9093:9093\n```\n\nIn a separate terminal, test the health endpoint:\n\n```\ncurl -sf http://localhost:9093/-/healthy && echo \"Alertmanager is healthy\"\n```\n\nYou should see:\n\n```\nAlertmanager is healthy\n```\n\nYou can also check the Alertmanager API status:\n\n```\ncurl -sf http://localhost:9093/api/v2/status | jq .cluster.status\n```\n\nExpected output:\n\n```\n\"ready\"\n```\n\n

\n\n### Step 6: Clean Up\n\n

\n\nUninstall the chart and delete the namespace to remove all resources:\n\n```bash\nhelm uninstall my-prometheus-alertmanager -n prometheus-alertmanager\nkubectl delete namespace prometheus-alertmanager\n```\n\n

\n\n\n---\n\n

\n\n## {{icon-info-circle}}Terms & Info\n\n

\n\n### Trademark\n\n

\n\nThis 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.\n\n\n{{if-anonymous}} \n\n

\n\n### Disclaimer\n\n

\n\n\nImages 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](https://www.minimus.io/terms-of-use).\n\n{{/if-anonymous}}\n\n\n

\n","ociDigest","sha256:fa1310568bbdd1980659eb4e8fb6ddd6bf4439df20f1f12fdae4ee91225e2ade","tarballDigest","sha256:e35d8c9d2f226c4e5d95dc2b7c977f1bd1feb2a309c491fd60d1a140088c988c","infra",18,"prometheus","Prometheus is a monitoring system and time series database.","2025-10-28T14:04:26.330076Z","2026-09-24T06:45:46.472219Z",[185],"https://prometheus-community.github.io/helm-charts/prometheus:29.33.0",{"_44":180,"_153":164,"_154":181,"_156":179,"_128":168,"_130":168,"_157":182,"_159":183,"_161":184},[174,175],84,{"_44":178,"_146":60,"_113":165,"_148":179},{"_44":176,"_146":60,"_113":147,"_148":177},1905,"v0.94.0",1904,"v3.14.0",798,"29.33.0","

\n\n# Prometheus Helm Chart\n\nPrometheus is a monitoring system and time series database. The Prometheus Helm chart automates deployment and configuration of Prometheus in Kubernetes clusters using Minimus images.\n\n\n## {{icon-list-search}} Prerequisites\n\n- A subscription to the Minimus images included in the chart\n- A running Kubernetes cluster (v1.19 or higher is recommended)\n- `kubectl` installed and configured\n- Helm v3.8 or higher for OCI support ([Installation instructions](https://helm.sh/docs/intro/install/))\n- Cluster Admin privileges\n\n

\n\n---\n\n

\n\n## {{icon-rocket}}Try It Out\n\nIn this example we will deploy Prometheus on a Kubernetes cluster using the Minimus Prometheus Helm chart. Prometheus will provide a full monitoring stack with metric collection, alerting, and visualization out of the box.\n\n

\n\n### Step 1: Start Cluster\n\n

\n\n### Step 2: Create Secret\n\n

\n\nFirst, create a namespace:\n\n```\nkubectl create ns prometheus\n```\n\nNext, create a Kubernetes secret for the Minimus token so Helm will be able to pull images from the Minimus registry:\n\n```\nkubectl create secret docker-registry minimus-registry \\\n --docker-server=reg.mini.dev \\\n --docker-username=minimus \\\n --docker-password={{pull-token}} \\\n --namespace=prometheus\n```\n\n

\n\n### Step 3: Deploy the Helm Chart\n\n

\n\nDeploy the Minimus Helm chart:\n\n```\nhelm install my-prometheus {{oci-url}} \\\n -n prometheus \\\n --wait\n```\n\nIf 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`:\n\n```\nhelm install my-prometheus {{oci-url}} \\\n -f values.yaml \\\n -n prometheus \\\n --wait\n```\n\n

\n\n### Step 4: Verify Prometheus is Running\n\n

\n\nConfirm the chart deployed successfully and all components started:\n\n```\nkubectl get pods -n prometheus\n```\n\nYou should see output similar to:\n\n```\nNAME READY STATUS RESTARTS AGE\nmy-prometheus-server-xxxxxxxxx-xxxxx 2/2 Running 0 2m\nmy-prometheus-prometheus-alertmanager-0 1/1 Running 0 2m\nmy-prometheus-kube-state-metrics-xxxxxxxxx-xxxxx 1/1 Running 0 2m\nmy-prometheus-prometheus-node-exporter-xxxxx 1/1 Running 0 2m\nmy-prometheus-prometheus-pushgateway-xxxxxxxxx-xxxxx 1/1 Running 0 2m\n```\n\n

\n\n### Step 5: Test HTTP Endpoint\n\n

\n\nForward the Prometheus server port to your local machine:\n\n```\nkubectl port-forward svc/my-prometheus-server 9090:80 -n prometheus\n```\n\nIn another terminal, verify the health endpoint responds:\n\n```\ncurl -sf http://localhost:9090/-/healthy\n```\n\nYou should see:\n\n```\nPrometheus Server is Healthy.\n```\n\nQuery the Prometheus API to confirm metric collection is working:\n\n```\ncurl -s http://localhost:9090/api/v1/query?query=up | jq '.data.result | length'\n```\n\nA non-zero result confirms Prometheus is actively scraping targets.\n\n

\n\n### Step 6: Clean Up\n\n

\n\nUninstall the chart and delete the namespace to remove all resources:\n\n```bash\nhelm uninstall my-prometheus -n prometheus\nkubectl delete namespace prometheus\n```\n\n

\n","sha256:5b0d1998f59c50570a5af8806ae27acf5a27f78cd2190f6ba0c2d6f324014be3","sha256:9cc75f31cabc0477890f3bc4bac7e6edb6c95e0c999121b748ae507d8ff085ee","utils",109,"kube-prometheus-stack","kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.","2026-04-15T07:20:25.694614Z","2026-07-26T17:24:12.683095Z",[163],"https://prometheus-community.github.io/helm-charts/kube-prometheus-stack:87.0.1",{"_44":221,"_153":186,"_154":222,"_156":210,"_128":223,"_130":190,"_157":224,"_159":225,"_161":226},[198,199,200,201,202,203,204],"minimusVulnsCount",111,416,{"_44":218,"_146":60,"_113":219,"_148":220},{"_44":216,"_146":60,"_113":165,"_148":217},{"_44":214,"_146":60,"_113":215,"_148":210},{"_44":212,"_146":60,"_113":126,"_148":213},{"_44":211,"_146":60,"_113":147,"_148":210},{"_44":208,"_146":60,"_113":209,"_148":210},{"_44":205,"_146":60,"_113":206,"_148":207},1198,"thanos","v0.41.0",1197,"prometheus-operator","v0.92.0",1196,1195,"v0.33.0",1194,"prometheus-admission-webhook",1193,"v3.12.0",1192,"kube-webhook-certgen","1.15.1",446,"87.0.1","2026-07-13T12:01:26.210728Z","

\n\n# kube-prometheus-stack Helm Chart\n\nkube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator. The kube-prometheus-stack Helm chart automates deployment and configuration of the Prometheus monitoring stack in Kubernetes clusters using Minimus images.\n\n\n## {{icon-list-search}} Prerequisites\n\n- A subscription to the Minimus images included in the chart\n- A running Kubernetes cluster (v1.25 or higher is recommended)\n- `kubectl` installed and configured\n- Helm v3.8 or higher for OCI support ([Installation instructions](https://helm.sh/docs/intro/install/))\n- Cluster Admin privileges\n\n**Note**: kube-prometheus-stack installs CRDs (Custom Resource Definitions) for Prometheus, Alertmanager, ServiceMonitors, PodMonitors, and related Prometheus Operator resources. Installing these CRDs requires cluster-admin privileges.\n\n

\n\n---\n\n

\n\n## {{icon-rocket}}Try It Out\n\nIn this example we will deploy the Prometheus monitoring stack on a Kubernetes cluster using the Minimus kube-prometheus-stack Helm chart. Out of the box you get Prometheus, Alertmanager, Grafana, node-exporter, kube-state-metrics, and the Prometheus Operator, wired together for end-to-end cluster monitoring.\n\n

\n\n### Step 1: Start Cluster\n\n

\n\n### Step 2: Create Namespace\n\n

\n\nCreate a namespace:\n\n```\nkubectl create ns kube-prometheus-stack\n```\n\n{{if-enterprise}}\n\nNext, create a Kubernetes secret for the Minimus token:\n\n```\nkubectl create secret docker-registry minimus-registry \\\n --docker-server=reg.mini.dev \\\n --docker-username=minimus \\\n --docker-password={{pull-token}} \\\n --namespace=kube-prometheus-stack\n```\n\n{{/if-enterprise}}\n\n

\n\n### Step 3: Deploy the Helm Chart\n\n

\n\nDeploy the Minimus Helm chart:\n\n```\nhelm install my-kube-prometheus-stack {{oci-url}} \\\n --version {{chart-version}} \\\n -n kube-prometheus-stack \\\n --wait\n```\n\nIf 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`:\n\n```\nhelm install my-kube-prometheus-stack {{oci-url}} \\\n --version {{chart-version}} \\\n -f values.yaml \\\n -n kube-prometheus-stack \\\n --wait\n```\n\n

\n\n### Step 4: Verify kube-prometheus-stack is Running\n\n

\n\nConfirm the chart deployed successfully and all components started:\n\n```\nkubectl get pods -n kube-prometheus-stack\n```\n\nYou should see output similar to:\n\n```\nNAME READY STATUS RESTARTS AGE\nmy-kube-prometheus-stack-grafana-xxxxxxxxx-xxxxx 3/3 Running 0 2m\nmy-kube-prometheus-stack-kube-state-metrics-xxxxxxxxx-xxxxx 1/1 Running 0 2m\nmy-kube-prometheus-stack-operator-xxxxxxxxx-xxxxx 1/1 Running 0 2m\nmy-kube-prometheus-stack-prometheus-node-exporter-xxxxx 1/1 Running 0 2m\nalertmanager-my-kube-prometheus-stack-alertmanager-0 2/2 Running 0 2m\nprometheus-my-kube-prometheus-stack-prometheus-0 2/2 Running 0 2m\n```\n\n

\n\n### Step 5: Test the Monitoring Stack\n\n

\n\nPort-forward to the Prometheus service and confirm it is healthy:\n\n```\nkubectl port-forward svc/my-kube-prometheus-stack-prometheus -n kube-prometheus-stack 9090:9090\n```\n\nIn another terminal, query the health endpoint — it should return `Prometheus Server is Healthy.`:\n\n```\ncurl -sf http://localhost:9090/-/healthy\n```\n\nYou can also reach the Grafana dashboards. Port-forward the Grafana service:\n\n```\nkubectl port-forward svc/my-kube-prometheus-stack-grafana -n kube-prometheus-stack 3000:80\n```\n\nOpen `http://localhost:3000` and log in as `admin`. Retrieve the password with:\n\n```\nkubectl -n kube-prometheus-stack get secret my-kube-prometheus-stack-grafana -o jsonpath=\"{.data.admin-password}\" | base64 -d\n```\n\n

\n\n### Step 6: Clean Up\n\n

\n\nUninstall the chart and delete the namespace to remove all resources:\n\n```\nhelm uninstall my-kube-prometheus-stack -n kube-prometheus-stack\nkubectl delete namespace kube-prometheus-stack\n```\n\n

\n\n---\n\n

\n\n## {{icon-info-circle}}Terms & Info\n\n

\n\n### Trademark\n\n

\n\n### Disclaimer\n\n

","sha256:a567d491f0e3de3c8f9852c740a6acd59da7e07b407ff5b6385f2aaf9be096ea","sha256:be84d9593177586ae219d52927d652e10fe1c7e43bad601ac1aabf8a313c46a1",115737,[163],"thirdPartyImageName","quay.io/prometheus-operator/prometheus-config-reloader:v0.92.1","2026-01-22T07:59:24.654138Z","2026-09-24T03:38:42.564008Z","private","isCustom","groups",[165,126],"shortDescription","published","family","edition","vanilla","fips",23,"webappURL","https://images.minimus.io","docsURL","https://docs.minimus.io/","docsMap",{"_256":257,"_258":259,"_260":26,"_261":262,"_263":264,"_265":266,"_267":268,"_269":270,"_271":26,"_272":26,"_273":26,"_274":275,"_276":277,"_278":279,"_280":281,"_282":283,"_284":26,"_285":286,"_287":26,"_288":26,"_289":26,"_290":26,"_291":26,"_292":26,"_293":26,"_294":26,"_295":26,"_296":26,"_297":298,"_299":300,"_301":302,"_303":304,"_305":306,"_307":308,"_309":26,"_310":26,"_311":26,"_312":26,"_313":314,"_315":26,"_316":317,"_318":319,"_320":321,"_322":321,"_323":324,"_325":26,"_326":26,"_327":328,"_329":330,"_331":332,"_333":334,"_335":336},"user","isAnonymous","isTokensExpired","license","cookiebotCBID","40e95942-a9eb-491e-8406-2f08417ec73b","/","https://docs.minimus.io","/actions","https://docs.minimus.io/remediate/actions","/actions/?","/actions/create","https://docs.minimus.io/remediate/create-action","/advisories","https://docs.minimus.io/remediate/advisories","/advisories/?","https://docs.minimus.io/remediate/cve-advisory","/advisories/?/exploitability","https://docs.minimus.io/remediate/threat-intel#threat-intel","/advisories/?/packages","https://docs.minimus.io/remediate/cve-advisory#status-history","/advisories/?/packages/?","/advisories/?/references","/advisories/?/severity","/charts","https://docs.minimus.io/foundations/helm-charts","/creator/list","https://docs.minimus.io/enterprise-edition/image-creator","/creator/files","https://docs.minimus.io/enterprise-edition/file-bundles","/supply-chain-protection","https://docs.minimus.io/enterprise-edition/supply-chain","/images","https://docs.minimus.io/gallery","/images/?","/images/?/changelog","https://docs.minimus.io/foundations/image-card#changelog","/images/?/changelog/?","/images/?/changelog/?/versions/?/?","/images/?/changelog/?/versions/?/?/exploitability","/images/?/changelog/?/versions/?/?/packages","/images/?/changelog/?/versions/?/?/packages/?","/images/?/changelog/?/versions/?/?/references","/images/?/changelog/?/versions/?/?/severity","/images/?/changelog/?/versions/?/digest-history","/images/?/lines","/images/?/lines/?","/images/?/lines/?/versions/?","https://docs.minimus.io/foundations/image-version","/images/?/lines/?/versions/?/digest-history","https://docs.minimus.io/foundations/image-version#digest-history","/images/?/lines/?/versions/?/sbom","https://docs.minimus.io/foundations/image-version#sbom","/images/?/lines/?/versions/?/specification","https://docs.minimus.io/foundations/image-version#specification","/images/?/lines/?/versions/?/vulnerabilities","https://docs.minimus.io/foundations/image-version#vulnerabilities","/images/?/risk-reduction","https://docs.minimus.io/foundations/image-card#risk-reduction","/images/?/risk-reduction/?","/images/?/risk-reduction/?/exploitability","/images/?/risk-reduction/?/references","/images/?/risk-reduction/?/severity","/images/?/compliance/cis","https://docs.minimus.io/foundations/image-card#compliance","/manage","/manage/self-hosting","https://docs.minimus.io/manage/self-hosted-registry","/manage/subscription","https://docs.minimus.io/introduction/subscription","/manage/logs/activity-log","https://docs.minimus.io/manage/activity-log","/manage/logs/audit-log","/manage/tokens","https://docs.minimus.io/manage/token","/manage/tokens/create","/manage/tokens/delete/?","/manage/access/users","https://docs.minimus.io/manage/users","/manage/access/users/create","https://docs.minimus.io/manage/users#add-users","/manage/access/users/saml","https://docs.minimus.io/sso/saml","/manage/access/groups","https://docs.minimus.io/manage/user-groups","/manage/minicli","https://docs.minimus.io/enterprise-edition/minicli","toast","gtmID","GTM-56RQNQ3D","hubspotID","42541238"]

Switch to a FIPS validated image with ease!