[Metricbeat] Kubelet secure port is not covered in YAML and documentation

[dkeightley]

Opening this issue for discussion around updates to metricbeat YAML/documentation

The Kubelet secure port (10250/TCP) used for authenticated communication is not covered in the YAML example and documentation.

Use of the read-only Kubelet port (10255/TCP) is now less common and discouraged, as such the suggestion for OpenShift also applies for Kubernetes, should this be amended?

[ChrsMark]

+1 on this. I also had this problem while playing with minikube.

Minikube version:

minikube version: v1.6.1
commit: 42a9df4854dcea40ec187b6b8f9a910c6038f81a

Metricbeat logs:

2020-02-03T15:20:15.919Z	INFO	module/wrapper.go:252	Error fetching data for metricset kubernetes.system: error doing HTTP request to fetch 'system' Metricset data: error making http request: Get http://localhost:10255/stats/summary: dial tcp 127.0.0.1:10255: connect: connection refused
2020-02-03T15:20:15.920Z	INFO	module/wrapper.go:252	Error fetching data for metricset kubernetes.volume: error doing HTTP request to fetch 'volume' Metricset data: error making http request: Get http://localhost:10255/stats/summary: dial tcp 127.0.0.1:10255: connect: connection refused
2020-02-03T15:20:16.131Z	INFO	module/wrapper.go:252	Error fetching data for metricset kubernetes.container: error doing HTTP request to fetch 'container' Metricset data: error making http request: Get http://localhost:10255/stats/summary: dial tcp 127.0.0.1:10255: connect: connection refused
2020-02-03T15:20:16.177Z	INFO	module/wrapper.go:252	Error fetching data for metricset kubernetes.pod: error doing HTTP request to fetch 'pod' Metricset data: error making http request: Get http://localhost:10255/stats/summary: dial tcp 127.0.0.1:10255: connect: connection refused
2020-02-03T15:20:16.221Z	INFO	module/wrapper.go:252	Error fetching data for metricset kubernetes.node: error doing HTTP request to fetch 'node' Metricset data: error making http request: Get http://localhost:10255/stats/summary: dial tcp 127.0.0.1:10255: connect: connection refused

I had to manually re-enable the read-only Kubelet port (10255/TCP) by adding --read-only-port=10255 flag in /etc/systemd/system/kubelet.service.d/10-kubeadm.conf in kubelet execution.