# How do I get the Infrastructure map working for Kubernetes Pods?

**URL:** <https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731>\
**Category:** Metrics\
**Created:** [November 13, 2019, 3:39pm UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731 "2019-11-13T15:39:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Neely](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@Richard\_Neely](https://discuss.elastic.co/u/Richard_Neely)\
**Post date:** [November 13, 2019, 3:39pm UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731/1 "2019-11-13T15:39:41Z")

</div>

All of my pods show up but metrics report as zero. Kube state metrics is running metrics are getting indexed into the metricbeat index. You can also see them on the Discover tab but nothing here. Running 6.8.3 across the board.

 ![53%20AM](https://us1.discourse-cdn.com/elastic/original/3X/f/7/f716df77a19b636c67af73b2c87161f0fb64517d.png)

---

<div class="post-metadata">

**Author:** ![simianhacker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simianhacker/32/3383_2.png) [@simianhacker](https://discuss.elastic.co/u/simianhacker)\
**Post date:** [November 18, 2019, 11:35pm UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731/2 "2019-11-18T23:35:52Z")

</div>

@Richard_Neely Did you deploy Metricbeat as a DaemonSet?

---

<div class="post-metadata">

**Author:** ![Richard\_Neely](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@Richard\_Neely](https://discuss.elastic.co/u/Richard_Neely)\
**Post date:** [November 19, 2019, 12:46am UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731/3 "2019-11-19T00:46:22Z")

</div>

Right now Metricbeat runs as a service on the box and talks to kubelet and kube-state-metrics. I do have filebeat deployed as a daemonset.

---

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [November 19, 2019, 8:11am UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731/4 "2019-11-19T08:11:36Z")

</div>

Hi @Richard_Neely,

Did you follow this guide? [https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-kubernetes.html](https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-kubernetes.html)

Can you explain how Metricbeat is running if not?

---

<div class="post-metadata">

**Author:** ![Richard\_Neely](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@Richard\_Neely](https://discuss.elastic.co/u/Richard_Neely)\
**Post date:** [November 19, 2019, 3:09pm UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731/5 "2019-11-19T15:09:38Z")

</div>

I just did. It's running as service on the box. It's able to hit the Kubelet service and also kube-state-metrics and pull the info in.

Config looks like this.

- module: kubernetes  
enabled: true  
metricsets:
  - node
  - system
  - pod
  - container  
period: 2m  
hosts: ["localhost:10255"]

# State metrics from kube-state-metrics service:

- module: kubernetes  
enabled: true  
metricsets:
  - state\_node
  - state\_deployment
  - state\_replicaset
  - state\_pod
  - state\_container  
period: 2m  
hosts: ["10.3.12.171:8080"]

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 17, 2019, 3:09pm UTC](https://discuss.elastic.co/t/how-do-i-get-the-infrastructure-map-working-for-kubernetes-pods/207731/6 "2019-12-17T15:09:42Z")

</div>

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