github/deprecated-helm-charts
1
0
Fork 0
mirror of https://github.com/helm/charts.git synced 2026-08-23 22:37:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Prom-oper. Readme update of kube-proxy metrics bind address, pointing to multiple possible cm locations. (#18374)

Browse Source 
Signed-off-by: Tibo Beijen <tibobeijen@gmail.com>
This commit is contained in:
Tibo Beijen
2019-11-08 07:36:15 -08:00
committed by Kubernetes Prow Robot
parent 205db45e2d
commit c5eed59e1f
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stable/prometheus-operator/Chart.yaml
+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.2
version: 8.1.3
appVersion: 0.34.0
tillerVersion: ">=2.12.0"
home: https://github.com/coreos/prometheus-operator
stable/prometheus-operator/README.md
+3 -1
View File
@@ -642,7 +642,9 @@ 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` in ConfigMap `kube-system/kube-proxy` if you want to collect them. For example:
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:
```
kubectl -n kube-system edit cm kube-proxy