Skip to content
Snippets Groups Projects
Commit d01cdf96 authored by seph's avatar seph Committed by Frederic Branczyk
Browse files

Update GKE kubelet scraping docs (#1682)

parent b7a9751f
No related branches found
No related tags found
No related merge requests found
...@@ -362,6 +362,8 @@ Should the Prometheus `/targets` page show kubelet targets, but not able to succ ...@@ -362,6 +362,8 @@ Should the Prometheus `/targets` page show kubelet targets, but not able to succ
As described in the [prerequisites](#prerequisites) section, in order to retrieve metrics from the kubelet token authentication and authorization must be enabled. Some Kubernetes setup tools do not enable this by default. As described in the [prerequisites](#prerequisites) section, in order to retrieve metrics from the kubelet token authentication and authorization must be enabled. Some Kubernetes setup tools do not enable this by default.
If you are using Google's GKE product, see [docs/GKE-cadvisor-support.md].
#### Authentication problem #### Authentication problem
The Prometheus `/targets` page will show the kubelet job with the error `403 Unauthorized`, when token authentication is not enabled. Ensure, that the `--authentication-token-webhook=true` flag is enabled on all kubelet configurations. The Prometheus `/targets` page will show the kubelet job with the error `403 Unauthorized`, when token authentication is not enabled. Ensure, that the `--authentication-token-webhook=true` flag is enabled on all kubelet configurations.
......
# Kubelet / cAdvisor special configuration updates for GKE # Kubelet / cAdvisor special configuration updates for GKE
In order to allow Prometheus to access the endpoints provided by the kubelet/cAdvisor on GKE we have to downgrade the scheme to HTTP (from HTTPS). Prior to GKE 1.11, the kubelet does not support token
authentication. Until it does, Prometheus must use HTTP (not HTTPS)
for scraping.
You can configure this behavior through kube-prometheus with:
```
local kp = (import 'kube-prometheus/kube-prometheus.libsonnet') +
(import 'kube-prometheus/kube-prometheus-insecure-kubelet.libsonnet') +
{
_config+:: {
# ... config here
}
};
```
Or, you can patch and re-apply your existing manifests with:
On linux: On linux:
...@@ -10,9 +24,9 @@ sed -i -e 's/https/http/g' \ ...@@ -10,9 +24,9 @@ sed -i -e 's/https/http/g' \
contrib/kube-prometheus/manifests/prometheus/prometheus-k8s-service-monitor-kubelet.yaml contrib/kube-prometheus/manifests/prometheus/prometheus-k8s-service-monitor-kubelet.yaml
``` ```
On MacOs: On MacOs:
``` ```
sed -i '' -e 's/https/http/g' \ sed -i '' -e 's/https/http/g' \
contrib/kube-prometheus/manifests/prometheus/prometheus-k8s-service-monitor-kubelet.yaml contrib/kube-prometheus/manifests/prometheus/prometheus-k8s-service-monitor-kubelet.yaml
``` ```
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment