mirror of
https://github.com/helm/charts.git
synced 2026-08-23 22:37:45 +00:00
[stable/prometheus-operator] Upgrading prometheus version to v2.5.0 (#9710)
* Upgrading operator, prometheus and alertmanager versions - Upgrading prometheus-operator version to 0.26.0 - Upgrading prometheus version to 2.5.0 - Upgrading alertmanager version to 0.15.3 - Tested on GKE by installing prometheus operator with above versions. - helm lint passed. Signed-off-by: Harshal Shah <harshal2623@gmail.com> * Removing operator version upgrade Keeping prometheus and alertmanager upgrades intact. Signed-off-by: Harshal Shah <harshal2623@gmail.com> * Fixing the chart app version Signed-off-by: Harshal Shah <harshal2623@gmail.com>
This commit is contained in:
Harshal Shah
committed by
Kubernetes Prow Robot
Kubernetes Prow Robot
parent
7c49292204
commit
eb4180bd15
@@ -0,0 +1,8 @@
|
||||
# Contributing Guidelines
|
||||
## How to contribute to this chart
|
||||
1. Fork this repository, develop and test your Chart.
|
||||
1. Bump the chart version for every change.
|
||||
1. Ensure PR title has the prefix `[stable/prometheus-operator]`
|
||||
1. Check for changes of RBAC rules.
|
||||
1. Check for changes in CRD specs.
|
||||
1. PR must pass the linter (`helm lint`)
|
||||
@@ -9,7 +9,7 @@ name: prometheus-operator
|
||||
sources:
|
||||
- https://github.com/coreos/prometheus-operator
|
||||
- https://coreos.com/operators/prometheus
|
||||
version: 0.1.29
|
||||
version: 0.1.30
|
||||
appVersion: "0.25.0"
|
||||
home: https://github.com/coreos/prometheus-operator
|
||||
keywords:
|
||||
|
||||
@@ -86,12 +86,12 @@ The following tables lists the configurable parameters of the prometheus-operato
|
||||
| `prometheusOperator.tolerations` | Tolerations for use with node taints https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ | `[]` |
|
||||
| `prometheusOperator.affinity` | Assign the prometheus operator to run on specific nodes https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ | `{}` |
|
||||
| `prometheusOperator.image.repository` | Repository for prometheus operator image | `quay.io/coreos/prometheus-operator` |
|
||||
| `prometheusOperator.image.tag` | Tag for prometheus operator image | `v0.24.0` |
|
||||
| `prometheusOperator.image.tag` | Tag for prometheus operator image | `v0.25.0` |
|
||||
| `prometheusOperator.image.pullPolicy` | Pull policy for prometheus operator image | `IfNotPresent` |
|
||||
| `prometheusOperator.configmapReloadImage.repository` | Repository for configmapReload image | `quay.io/coreos/configmap-reload` |
|
||||
| `prometheusOperator.configmapReloadImage.tag` | Tag for configmapReload image | `v0.0.1` |
|
||||
| `prometheusOperator.prometheusConfigReloaderImage.repository` | Repository for config-reloader image | `quay.io/coreos/prometheus-config-reloader` |
|
||||
| `prometheusOperator.prometheusConfigReloaderImage.tag` | Tag for config-reloader image | `v0.24.0` |
|
||||
| `prometheusOperator.prometheusConfigReloaderImage.tag` | Tag for config-reloader image | `v0.25.0` |
|
||||
| `prometheusOperator.hyperkubeImage.repository` | Repository for hyperkube image used to perform maintenance tasks | `gcr.io/google-containers/hyperkube` |
|
||||
| `prometheusOperator.hyperkubeImage.tag` | Tag for hyperkube image used to perform maintenance tasks | `v1.12.1` |
|
||||
| `prometheusOperator.hyperkubeImage.repository` | Image pull policy for hyperkube image used to perform maintenance tasks | `IfNotPresent` |
|
||||
@@ -120,7 +120,7 @@ The following tables lists the configurable parameters of the prometheus-operato
|
||||
| `prometheus.prometheusSpec.serviceMonitorSelector` | ServiceMonitors to be selected for target discovery. | `{}` |
|
||||
| `prometheus.prometheusSpec.serviceMonitorNamespaceSelector` | Namespaces to be selected for ServiceMonitor discovery. If nil, only check own namespace. | `{}` |
|
||||
| `prometheus.prometheusSpec.image.repository` | Base image to use for a Prometheus deployment. | `quay.io/prometheus/prometheus` |
|
||||
| `prometheus.prometheusSpec.image.tag` | Tag of Prometheus container image to be deployed. | `v2.3.4` |
|
||||
| `prometheus.prometheusSpec.image.tag` | Tag of Prometheus container image to be deployed. | `v2.5.0` |
|
||||
| `prometheus.prometheusSpec.paused` | When a Prometheus deployment is paused, no actions except for deletion will be performed on the underlying objects. | `false` |
|
||||
| `prometheus.prometheusSpec.replicas` | Number of instances to deploy for a Prometheus deployment. | `1` |
|
||||
| `prometheus.prometheusSpec.retention` | Time duration Prometheus shall retain data for. Must match the regular expression `[0-9]+(ms\|s\|m\|h\|d\|w\|y)` (milliseconds seconds minutes hours days weeks years). | `120h` |
|
||||
@@ -171,7 +171,7 @@ The following tables lists the configurable parameters of the prometheus-operato
|
||||
| `alertmanager.service.annotations` | Alertmanager Service annotations | `{}` |
|
||||
| `alertmanager.config` | Provide YAML to configure Alertmanager. See https://prometheus.io/docs/alerting/configuration/#configuration-file. The default provided works to suppress the DeadMansSwitch alert from `defaultRules.create` | `{"global":{"resolve_timeout":"5m"},"route":{"group_by":["job"],"group_wait":"30s","group_interval":"5m","repeat_interval":"12h","receiver":"null","routes":[{"match":{"alertname":"DeadMansSwitch"},"receiver":"null"}]},"receivers":[{"name":"null"}]}` |
|
||||
| `alertmanager.alertmanagerSpec.podMetadata` | Standard object’s metadata. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#metadata Metadata Labels and Annotations gets propagated to the prometheus pods. | `{}` |
|
||||
| `alertmanager.alertmanagerSpec.image.tag` | Tag of Alertmanager container image to be deployed. | `v0.15.2` |
|
||||
| `alertmanager.alertmanagerSpec.image.tag` | Tag of Alertmanager container image to be deployed. | `v0.15.3` |
|
||||
| `alertmanager.alertmanagerSpec.image.repository` | Base image that is used to deploy pods, without tag. | `quay.io/prometheus/alertmanager` |
|
||||
| `alertmanager.alertmanagerSpec.secrets` | Secrets is a list of Secrets in the same namespace as the Alertmanager object, which shall be mounted into the Alertmanager Pods. The Secrets are mounted into /etc/alertmanager/secrets/<secret-name>. | `[]` |
|
||||
| `alertmanager.alertmanagerSpec.configMaps` | ConfigMaps is a list of ConfigMaps in the same namespace as the Alertmanager object, which shall be mounted into the Alertmanager Pods. The ConfigMaps are mounted into /etc/alertmanager/configmaps/ | `[]` |
|
||||
|
||||
@@ -157,7 +157,7 @@ alertmanager:
|
||||
##
|
||||
image:
|
||||
repository: quay.io/prometheus/alertmanager
|
||||
tag: v0.15.2
|
||||
tag: v0.15.3
|
||||
|
||||
## Secrets is a list of Secrets in the same namespace as the Alertmanager object, which shall be mounted into the
|
||||
## Alertmanager Pods. The Secrets are mounted into /etc/alertmanager/secrets/.
|
||||
@@ -651,10 +651,10 @@ prometheus:
|
||||
##
|
||||
image:
|
||||
repository: quay.io/prometheus/prometheus
|
||||
tag: v2.4.3
|
||||
tag: v2.5.0
|
||||
|
||||
# repository: quay.io/coreos/prometheus
|
||||
# tag: v2.4.3
|
||||
# tag: v2.5.0
|
||||
|
||||
## Tolerations for use with node taints
|
||||
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
|
||||
|
||||
@@ -156,7 +156,7 @@ alertmanager:
|
||||
##
|
||||
image:
|
||||
repository: quay.io/prometheus/alertmanager
|
||||
tag: v0.15.2
|
||||
tag: v0.15.3
|
||||
|
||||
## Secrets is a list of Secrets in the same namespace as the Alertmanager object, which shall be mounted into the
|
||||
## Alertmanager Pods. The Secrets are mounted into /etc/alertmanager/secrets/.
|
||||
@@ -648,10 +648,10 @@ prometheus:
|
||||
##
|
||||
image:
|
||||
repository: quay.io/prometheus/prometheus
|
||||
tag: v2.4.3
|
||||
tag: v2.5.0
|
||||
|
||||
# repository: quay.io/coreos/prometheus
|
||||
# tag: v2.4.3
|
||||
# tag: v2.5.0
|
||||
|
||||
## Tolerations for use with node taints
|
||||
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
|
||||
|
||||
Reference in New Issue
Block a user