Update README.md (#18816)

Signed-off-by: vas <vasily.sliouniaev@jet.com>
This commit is contained in:
Vasily Sliouniaev
2019-11-12 07:52:14 -08:00
committed by Kubernetes Prow Robot
parent aa76c853d8
commit 036662801e
2 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -12,7 +12,7 @@ sources:
- https://github.com/coreos/kube-prometheus
- https://github.com/coreos/prometheus-operator
- https://coreos.com/operators/prometheus
version: 8.1.7
version: 8.1.8
appVersion: 0.34.0
tillerVersion: ">=2.12.0"
home: https://github.com/coreos/prometheus-operator
+2 -2
View File
@@ -33,7 +33,7 @@ This chart bootstraps a [prometheus-operator](https://github.com/coreos/promethe
## Prerequisites
- Kubernetes 1.10+ with Beta APIs
- Helm 2.10+ (For a workaround using an earlier version see [below](#helm-210-workaround))
- Helm 2.12+ (If using Helm < 2.14, [see below for CRD workaround](#Helm-fails-to-create-CRDs))
## Installing the Chart
@@ -644,7 +644,7 @@ The PVC will take ownership of the PV and when you create a release using a pers
### KubeProxy
The metrics bind address of kube-proxy is default to `127.0.0.1:10249` that prometheus instances **cannot** access to. You should expose metrics by changing `metricsBindAddress` field value to `0.0.0.0:10249` if you want to collect them.
The metrics bind address of kube-proxy is default to `127.0.0.1:10249` that prometheus instances **cannot** access to. You should expose metrics by changing `metricsBindAddress` field value to `0.0.0.0:10249` if you want to collect them.
Depending on the cluster, the relevant part `config.conf` will be in ConfigMap `kube-system/kube-proxy` or `kube-system/kube-proxy-config`. For example: