Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes
squat Merge pull request #2029 from coreos/release-0.24
Merge changelog additions back into master
Latest commit d0cf2ee Oct 18, 2018
Failed to load latest commit information.
.github .github: request operator version in issues Jul 20, 2018
Documentation *: Update generated code and docs Oct 16, 2018
cmd make sure pipe characters are escaped in api docs table generation Oct 12, 2018
contrib/kube-prometheus Merge pull request #2020 from dlespiau/2018-10-16-bump-prometheus-ope… Oct 16, 2018
example Merge pull request #1953 from kmodules/k-1.12 Oct 17, 2018
hack hack: Fix generate in docker script to actually run the command. Oct 16, 2018
helm added v1 to capabilities in helm chart (#1729) Aug 9, 2018
jsonnet/prometheus-operator Merge pull request #1953 from kmodules/k-1.12 Oct 17, 2018
pkg Merge pull request #1953 from kmodules/k-1.12 Oct 17, 2018
scripts scripts: Enable minikube storage provisioner in e2e tests Sep 26, 2018
test test/e2e: Adjust TargetPort test Oct 15, 2018
vendor Merge pull request #1953 from kmodules/k-1.12 Oct 17, 2018
.editorconfig .editorconfig: Add configuration for yaml files Jul 24, 2018
.gitignore *: Refactor build system Jun 12, 2018
.header Update License header to 2018 Jan 30, 2018
.promu.yml Build system: Introduce promu to prometheus-operator Jan 30, 2017
.travis.yml *: Update to Go 1.11 Sep 5, 2018 Changelog: Add note about namespaces flag Oct 11, 2018 Add liecense, CoC, etc. Nov 1, 2016
DCO Add liecense, CoC, etc. Nov 1, 2016
Dockerfile security: Enforce nobody user and read only / (#1393) Jul 17, 2018
Gopkg.lock Merge pull request #1953 from kmodules/k-1.12 Oct 17, 2018
Gopkg.toml Merge pull request #1953 from kmodules/k-1.12 Oct 17, 2018
LICENSE Add liecense, CoC, etc. Nov 1, 2016
Makefile detect selinux enforcing mode and add :Z flag to docker run volume arg Oct 11, 2018
NOTICE Add liecense, CoC, etc. Nov 1, 2016
OWNERS OWNERS: Add metalmatze and s-urbaniak Sep 28, 2018 Merge pull request #1949 from mxinden/release Oct 9, 2018 Update documentation Sep 28, 2018
VERSION Bump version to 0.24 Oct 11, 2018
bundle.yaml Bump version to 0.24 Oct 11, 2018 update CoC Jan 4, 2018

Prometheus Operator

Build Status Go Report Card

Project status: beta Not all planned features are completed. The API, spec, status and other user facing objects may change, but in a backward compatible way.

The Prometheus Operator for Kubernetes provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances.

Once installed, the Prometheus Operator provides the following features:

  • Create/Destroy: Easily launch a Prometheus instance for your Kubernetes namespace, a specific application or team easily using the Operator.

  • Simple Configuration: Configure the fundamentals of Prometheus like versions, persistence, retention policies, and replicas from a native Kubernetes resource.

  • Target Services via Labels: Automatically generate monitoring target configurations based on familiar Kubernetes label queries; no need to learn a Prometheus specific configuration language.

For an introduction to the Prometheus Operator, see the initial blog post.

Prometheus Operator vs. kube-prometheus

The Prometheus Operator makes the Prometheus configuration Kubernetes native and manages and operates Prometheus and Alertmanager clusters. It is a piece of the puzzle regarding full end-to-end monitoring.

kube-prometheus combines the Prometheus Operator with a collection of manifests to help getting started with monitoring Kubernetes itself and applications running on top of it.


Version >=0.18.0 of the Prometheus Operator requires a Kubernetes cluster of version >=1.8.0. If you are just starting out with the Prometheus Operator, it is highly recommended to use the latest version.

If you have an older version of Kubernetes and the Prometheus Operator running, we recommend upgrading Kubernetes first and then the Prometheus Operator.


The Operator acts on the following custom resource definitions (CRDs):

  • Prometheus, which defines a desired Prometheus deployment. The Operator ensures at all times that a deployment matching the resource definition is running.

  • ServiceMonitor, which declaratively specifies how groups of services should be monitored. The Operator automatically generates Prometheus scrape configuration based on the definition.

  • PrometheusRule, which defines a desired Prometheus rule file, which can be loaded by a Prometheus instance containing Prometheus alerting and recording rules.

  • Alertmanager, which defines a desired Alertmanager deployment. The Operator ensures at all times that a deployment matching the resource definition is running.

To learn more about the CRDs introduced by the Prometheus Operator have a look at the design doc.


Install the Operator inside a cluster by running the following command:

kubectl apply -f bundle.yaml

Note: make sure to adapt the namespace in the ClusterRoleBinding if deploying in another namespace than the default namespace.

To run the Operator outside of a cluster:

hack/ <kubectl cluster name>


To remove the operator and Prometheus, first delete any custom resources you created in each namespace. The operator will automatically shut down and remove Prometheus and Alertmanager pods, and associated configmaps.

for n in $(kubectl get namespaces -o jsonpath={}); do
  kubectl delete --all --namespace=$n prometheus,servicemonitor,alertmanager

After a couple of minutes you can go ahead and remove the operator itself.

kubectl delete -f bundle.yaml

The operator automatically creates services in each namespace where you created a Prometheus or Alertmanager resources, and defines three custom resource definitions. You can clean these up now.

for n in $(kubectl get namespaces -o jsonpath={}); do
  kubectl delete --ignore-not-found --namespace=$n service prometheus-operated alertmanager-operated

kubectl delete --ignore-not-found customresourcedefinitions \ \ \



  • golang environment
  • docker (used for creating container images, etc.)
  • minikube (optional)


Ensure that you're running tests in the following path: $GOPATH/src/ as tests expect paths to match. If you're working from a fork, just add the forked repo as a remote and pull against your local coreos checkout before running tests.

Running unit tests:

make test-unit

Running end-to-end tests on local minikube cluster:

  1. minikube start --kubernetes-version=v1.10.0 --memory=4096 --extra-config=apiserver.Authorization.Mode=RBAC
  2. eval $(minikube docker-env) && make image - build Prometheus Operator docker image on minikube's docker
  3. make test-e2e


Many files (documentation, manifests, ...) in this repository are auto-generated. E.g. bundle.yaml originates from the Jsonnet files in /jsonnet/prometheus-operator. Before proposing a pull request:

  1. Commit your changes.
  2. Run make generate-in-docker.
  3. Commit the generated changes.


If you find a security vulnerability related to the Prometheus Operator, please do not report it by opening a GitHub issue, but instead please send an e-mail to the maintainers of the project found in the OWNERS file.