mirrors/prometheus-operator
mirrors/prometheus-operator
1
0
Fork 0
mirror of https://github.com/prometheus-operator/prometheus-operator.git synced 2025-04-21 19:49:46 +00:00
Code Activity

CHANGELOG.md: Add v0.20.0 & Next release entry

Browse source
This commit is contained in:
Max Leonard Inden 2018-06-05 11:33:19 +02:00
parent 7d08e3d69c
commit 528849e7a0
No known key found for this signature in database
GPG key ID: 5403C5464810BC26
1 changed files with 31 additions and 0 deletions

31
CHANGELOG.md
View file

@ -1,3 +1,34 @@
# Next release
* [CHANGE] Deprecate specification of Prometheus rules via ConfigMaps in favor of `PrometheusRule` CRDs
## 0.20.0 / 2018-06-05
With this release we introduce a new Custom Resource Definition - the
`PrometheusRule` CRD. It addresses the need for rule syntax validation and rule
selection accross namespaces. `PrometheusRule` replaces the configuration of
Prometheus rules via K8s ConfigMaps. There are two migration paths:
1. Automated live migration: If the Prometheus Operator finds Kubernetes
ConfigMaps that match the `RuleSelector` in a `Prometheus` specification, it
will convert them to matching `PrometheusRule` resources.
2. Manual migration: We provide a basic CLI tool to convert Kubernetes
ConfigMaps to `PrometheusRule` resources.
```bash
go get -u github.com/coreos/prometheus-operator/cmd/po-rule-migration
po-rule-migration \
--rule-config-map=<path-to-config-map> \
--rule-crds-destination=<path-to-rule-crd-destination>
```
* [FEATURE] Add leveled logging to Prometheus Operator (#1277)
* [FEATURE] Allow additional Alertmanager configuration in Prometheus CRD (#1338)
* [FEATURE] Introduce `PrometheusRule` Custom Resource Definition (#1333)
* [ENHANCEMENT] Allow Prometheus to consider all namespaces to find ServiceMonitors (#1278)
* [BUGFIX] Do not attempt to set default memory request for Prometheus 2.0 (#1275)
## 0.19.0 / 2018-04-25
* [FEATURE] Allow specifying additional Prometheus scrape configs via secret (#1246)