From 87ffc6329c76c9fd0784bb8cbb4cc86ecce97453 Mon Sep 17 00:00:00 2001 From: "David J. M. Karlsen" Date: Wed, 16 Jan 2019 01:08:25 +0100 Subject: [PATCH] upgrade prometheus to 2.6.1 (#10677) * upgrade prometheus to 2.6.1 Signed-off-by: David J. M. Karlsen * Obsoletes #10574 - it lacked DCO etc Signed-off-by: David J. M. Karlsen --- stable/prometheus/Chart.yaml | 4 ++-- stable/prometheus/README.md | 6 +++--- stable/prometheus/values.yaml | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/stable/prometheus/Chart.yaml b/stable/prometheus/Chart.yaml index 244168080b..bd5a3aa988 100755 --- a/stable/prometheus/Chart.yaml +++ b/stable/prometheus/Chart.yaml @@ -1,6 +1,6 @@ name: prometheus -version: 8.4.4 -appVersion: 2.6.0 +version: 8.4.5 +appVersion: 2.6.1 description: Prometheus is a monitoring system and time series database. home: https://prometheus.io/ icon: https://raw.githubusercontent.com/prometheus/prometheus.github.io/master/assets/prometheus_logo-cb55bb5c346.png diff --git a/stable/prometheus/README.md b/stable/prometheus/README.md index 224d7e384f..d9719beec7 100644 --- a/stable/prometheus/README.md +++ b/stable/prometheus/README.md @@ -46,11 +46,11 @@ Users of this chart will need to update their alerting rules to the new format b ## Upgrading from previous chart versions. -As of version 5.0, this chart uses Prometheus 2.1. This version of prometheus introduces a new data format and is not compatible with prometheus 1.x. It is recommended to install this as a new release, as updating existing releases will not work. See the [prometheus docs](https://prometheus.io/docs/prometheus/latest/migration/#storage) for instructions on retaining your old data. +As of version 5.0, this chart uses Prometheus 2.x. This version of prometheus introduces a new data format and is not compatible with prometheus 1.x. It is recommended to install this as a new release, as updating existing releases will not work. See the [prometheus docs](https://prometheus.io/docs/prometheus/latest/migration/#storage) for instructions on retaining your old data. ### Example migration -Assuming you have an existing release of the prometheus chart, named `prometheus-old`. In order to update to prometheus 2.1 while keeping your old data do the following: +Assuming you have an existing release of the prometheus chart, named `prometheus-old`. In order to update to prometheus 2.x while keeping your old data do the following: 1. Update the `prometheus-old` release. Disable scraping on every component besides the prometheus server, similar to the configuration below: @@ -227,7 +227,7 @@ Parameter | Description | Default `rbac.create` | If true, create & use RBAC resources | `true` `server.name` | Prometheus server container name | `server` `server.image.repository` | Prometheus server container image repository | `prom/prometheus` -`server.image.tag` | Prometheus server container image tag | `v2.6.0` +`server.image.tag` | Prometheus server container image tag | `v2.6.1` `server.image.pullPolicy` | Prometheus server container image pull policy | `IfNotPresent` `server.enableAdminApi` | If true, Prometheus administrative HTTP API will be enabled. Please note, that you should take care of administrative API access protection (ingress or some frontend Nginx with auth) before enabling it. | `false` `server.global.scrape_interval` | How frequently to scrape targets by default | `1m` diff --git a/stable/prometheus/values.yaml b/stable/prometheus/values.yaml index 21f458e52e..58d6ac6b35 100644 --- a/stable/prometheus/values.yaml +++ b/stable/prometheus/values.yaml @@ -517,7 +517,7 @@ server: ## image: repository: prom/prometheus - tag: v2.6.0 + tag: v2.6.1 pullPolicy: IfNotPresent ## prometheus server priorityClassName