Metricbeat fails to communicate with kubelet

Elastic Stack Beats
1

Hello,

I installed the metricbeat (daemonset) on kubernetes by applying the YAML files.
The metricbeat PODs were installed successfully, but there is a communication issue between metricbeat and kubelet due to certificate at 10250 port.

metricset.name:node @timestamp:January 18th 2019, 14:35:20.016 metricset.module:kubernetes metricset.host:dev-k8s-node2:10250 metricset.rtt:8,391 error.message:error making http request: Get https://dev-k8s-node2:10250/stats/summary: x509: certificate signed by unknown authority beat.name:dev-k8s-node2 beat.hostname:dev-k8s-node2 beat.version:6.5.4 host.name:dev-k8s-node2 _id:-H70YGgB-Ffh-dxO2BpO _type:doc _index:metricbeat-6.5.4-2019.01.18 _score: -

I changed the ConfigMap by applying the following in order to establish the connectivity, but with no success:

hosts: ["https://${HOSTNAME}:10250"]
bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
ssl.certificate_authorities:
- /var/run/secrets/kubernetes.io/serviceaccount/ca.crt

Is there any documentation about this?

thank you.

2

this was resolved by adding ssl.verification_mode: "none" at the configmap.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.