History

flouthoc 4f3e106433 Change versions to fix memory.limit_in_bytes: device or resource busy Change Operator version to `to fix memory.limit_in_bytes: device or resource busy` Issue is that the upgrade for docker to fix CVE-2019-5736 has required that runC be loaded into memory: lxc/lxc@6400238. The data is about 12Mi in size, so it's too big to work with the 10Mi containers that Prometheus Operator creates for the configuration reloader side-cars. Fixed in newer Versions of Prometheus Operators therefore changing versions. References: https://github.com/helm/charts/issues/11447 https://github.com/coreos/prometheus-operator/pull/2403		2019-05-25 16:04:03 +05:30
..
README.md	bump prometheus-operator version and deploy file	2018-12-11 14:02:14 +08:00
addon.yaml	bump prometheus-operator version and deploy file	2018-12-11 14:02:14 +08:00
sync-repo.sh	bump prometheus-operator version and deploy file	2018-12-11 14:02:14 +08:00
v0.19.0.yaml	Merge pull request #6305 from bzon/master	2019-01-09 03:51:31 -08:00
v0.26.0.yaml	Remove duplicate Deployment for prometheus-operator	2018-12-23 23:23:29 +00:00
v0.29.0.yaml	Change versions to fix memory.limit_in_bytes: device or resource busy	2019-05-25 16:04:03 +05:30

README.md

Prometheus Operator Addon

Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes. This addon deploy prometheus-operator and kube-prometheus in a kops cluster.

Prerequisites

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.

Usage

Deploy To Cluster

kubectl apply -f https://raw.githubusercontent.com/kubernetes/kops/master/addons/prometheus-operator/v0.26.0.yaml

Updating the addon

Run the script below.

addons/prometheus-operator/sync-repo.sh "v0.26.0"