Today I set up metricbeat on a kubernetes cluster and cant make it connect to the elastic search logging pod.
I followed this example here: https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-kubernetes.html
The singleton instance seems to be fine connecting, but the other deamons are not - thats the output of one of the deamons:
2018/02/22 12:29:12.156143 tcp.go:36: WARN DNS lookup failure "elasticsearch-logging.kube-system.svc.cluster.local": lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
2018/02/22 12:29:13.156380 output.go:74: ERR Failed to connect: Get http://elasticsearch-logging.kube-system.svc.cluster.local:9200: lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
2018/02/22 12:29:13.157815 tcp.go:36: WARN DNS lookup failure "elasticsearch-logging.kube-system.svc.cluster.local": lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
2018/02/22 12:29:15.158009 output.go:74: ERR Failed to connect: Get http://elasticsearch-logging.kube-system.svc.cluster.local:9200: lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
2018/02/22 12:29:15.173593 tcp.go:36: WARN DNS lookup failure "elasticsearch-logging.kube-system.svc.cluster.local": lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
2018/02/22 12:29:19.173815 output.go:74: ERR Failed to connect: Get http://elasticsearch-logging.kube-system.svc.cluster.local:9200: lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
2018/02/22 12:29:19.178753 tcp.go:36: WARN DNS lookup failure "elasticsearch-logging.kube-system.svc.cluster.local": lookup elasticsearch-logging.kube-system.svc.cluster.local: no such host
Where's that error coming from?