1
0
Fork 0
mirror of https://github.com/prometheus-operator/prometheus-operator.git synced 2025-04-16 09:16:38 +00:00
prometheus-operator/helm/alertmanager
tmestdagh e7c84c6cfb Added support for multiple hostnames to alertmanager/prometheus/grafana (#1290)
* Added support for multiple hostnames to alertmanager/prometheus/grafana
Ingress

* Fixed grafana/NOTES.txt and kube-prometheus/NOTES.txt

* Fixed kube-prometheus/NOTES.txt
2018-05-01 17:10:24 +02:00
..
templates Added support for multiple hostnames to alertmanager/prometheus/grafana (#1290) 2018-05-01 17:10:24 +02:00
.helmignore Added kube-prometheus chart with end-to-end exporters (#277) 2017-05-30 18:01:40 -07:00
Chart.yaml Added support for multiple hostnames to alertmanager/prometheus/grafana (#1290) 2018-05-01 17:10:24 +02:00
README.md Added support for multiple hostnames to alertmanager/prometheus/grafana (#1290) 2018-05-01 17:10:24 +02:00
values.yaml Added support for multiple hostnames to alertmanager/prometheus/grafana (#1290) 2018-05-01 17:10:24 +02:00

alertmanager

Installs a Prometheus Alertmanager instance using the CoreOS prometheus-operator.

TL;DR;

$ helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
$ helm install coreos/alertmanager

Introduction

This chart bootstraps an Alertmanager deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Installing the Chart

To install the chart with the release name my-release:

$ helm install coreos/alertmanager --name my-release

The command deploys Alertmanager on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following tables lists the configurable parameters of the alertmanager chart and their default values.

Parameter Description Default
config Alertmanager configuration directives {}
externalUrl External URL at which Alertmanager will be reachable ""
routePrefix Prefix used to register routes "/"
image.repository Image quay.io/prometheus/alertmanager
image.tag Image tag v0.12.0
ingress.enabled If true, Alertmanager Ingress will be created false
ingress.annotations Annotations for Alertmanager Ingress` {}
ingress.labels Labels for Alertmanager Ingress` {}
ingress.hosts Alertmanager Ingress hosts []
ingress.tls TLS configuration for Alertmanager Ingress []
nodeSelector Node labels for pod assignment {}
paused If true, the Operator won't process any Alertmanager configuration changes false
podAntiAffinity If "soft", the scheduler attempts to place Alertmanager replicas on different nodes. If "hard" the scheduler is required to place them on different nodes. If "" (empty) then no anti-affinity rules will be configured. soft
prometheusRules Prometheus rules [templates/alertmanager.rules.yaml](templates/alertmanager.rules.yaml)
replicaCount Number of Alertmanager replicas desired 1
resources Pod resource requests & limits {}
service.annotations Annotations to be added to the Alertmanager Service {}
service.clusterIP Cluster-internal IP address for Alertmanager Service ""
service.externalIPs List of external IP addresses at which the Alertmanager Service will be available []
service.loadBalancerIP External IP address to assign to Alertmanager Service ""
service.loadBalancerSourceRanges List of client IPs allowed to access Alertmanager Service []
service.nodePort Port to expose Alertmanager Service on each node 39093
service.type Alertmanager Service type ClusterIP
storageSpec Alertmanager StorageSpec for persistent data {}

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example, $ helm install coreos/alertmanager --name my-release --set externalUrl=http://alertmanager.example.com


Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

```console
$ helm install coreos/alertmanager --name my-release -f values.yaml

Tip: You can use the default values.yaml

CRD Resource Documentation