prometheus-operator

Installs prometheus-operator to create/configure/manage Prometheus clusters atop Kubernetes.

TL;DR;

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

Introduction

This chart bootstraps a prometheus-operator deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

• Kubernetes 1.4+ with Beta APIs & ThirdPartyResources enabled

RBAC

If role-based access control (RBAC) is enabled in your cluster, you may need to give Tiller (the server-side component of Helm) additional permissions. If RBAC is not enabled, be sure to set rbacEnable to false when installing the chart.

1. Create a ServiceAccount for Tiller in the kube-system namespace

$ kubectl -n kube-system create sa tiller

2. Create a ClusterRoleBinding for Tiller

# kubectl v1.5.x
$ cat <<EOF | kubectl create -f -
apiVersion: rbac.authorization.k8s.io/v1alpha1
kind: ClusterRoleBinding
metadata:
  name: tiller
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
  - kind: ServiceAccount
    name: tiller
    namespace: kube-system
EOF

# kubectl v1.6.x
$ kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller

3. Install Tiller, specifying the new ServiceAccount

$ helm init --service-account tiller

Installing the Chart

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

$ helm install --name my-release coreos/prometheus-operator

The command deploys prometheus-operator 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 prometheus-operator chart and their default values.

Parameter	Description	Default
configmapReload.repository	configmap-reload image	quay.io/coreos/configmap-reload
configmapReload.tag	configmap-reload tag	v0.0.1
global.hyperkube.repository	Hyperkube image	quay.io/coreos/hyperkube
global.hyperkube.tag	Hyperkube image tag	v1.7.6_coreos.0
global.hyperkube.pullPolicy	Hyperkube image pull policy	IfNotPresent
image.repository	Image	quay.io/coreos/prometheus-operator
image.tag	Image tag	v0.15.0
image.pullPolicy	Image pull policy	IfNotPresent
kubeletService.enable	If true, the operator will create a service for scraping kubelets	true
kubeletService.namespace	The namespace in which the kubelet service should be created	kube-system
kubeletService.name	The name of the kubelet service to be created	kubelet
nodeSelector	Node labels for pod assignment	{}
prometheusConfigReloader.repository	prometheus-config-reloader image	quay.io/coreos/prometheus-config-reloader
prometheusConfigReloader.tag	prometheus-config-reloader tag	v0.0.2
rbacEnable	If true, create & use RBAC resources	true
resources	Pod resource requests & limits	{}

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release coreos/prometheus-operator --set sendAnalytics=true

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

$ helm install --name my-release coreos/prometheus-operator -f values.yaml

Tip: You can use the default values.yaml