[bitnami/prometheus-operator]: Review fixes

Signed-off-by: Christian Kotzbauer <christian.kotzbauer@gmail.com>
This commit is contained in:
Christian Kotzbauer
2019-12-30 15:42:36 +01:00
parent 01afec7249
commit c8aada1bf8
2 changed files with 6 additions and 2 deletions
+1 -1
View File
@@ -2,7 +2,7 @@ apiVersion: v1
appVersion: 0.34.0
description: The Prometheus Operator for Kubernetes provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances.
name: prometheus-operator
version: 0.7.7
version: 0.8.0
keywords:
- prometheus
- alertmanager
+5 -1
View File
@@ -210,7 +210,7 @@ The following table lists the configurable parameters of the Prometheus Operator
| `prometheus.storageSpec` | Prometheus StorageSpec for persistent data | `{}` |
| `prometheus.priorityClassName` | Priority class assigned to the Pods | `` |
| `prometheus.containers` | Containers allows injecting additional containers | `[]` |
| `prometheus.additionalScrapeConfigsExternal` | Enable additional scrape configs that are managed externally to this chart | `false` |
| `prometheus.additionalScrapeConfigsExternal` | Enable additional scrape configs that are managed externally to this chart | `false` See [docs](#additionalScrape) for details. |
### Alertmanager Parameters
@@ -351,6 +351,10 @@ This chart includes a `values-production.yaml` file where you can find some para
+ logLevel: error
```
### <a name="additionalScrape"></a>Additonal scrape configurations
It is possible to inject externally managed scrape configurations in a ConfigMap by enabling `prometheus.additionalScrapeConfigsExternal`. The ConfigMap must exist in the same namespace when Prometheus is starting. Its name is generated using the `prometheus-operator.prometheus.fullname` template with a `-scrape-config` suffix. The file it contains has to be named `additional-scrape-configs.yaml`.
## Upgrading
```bash