# Packetbeat - Cannot add kubernetes metadata

**URL:** <https://discuss.elastic.co/t/packetbeat-cannot-add-kubernetes-metadata/263615>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [February 8, 2021, 2:36pm UTC](https://discuss.elastic.co/t/packetbeat-cannot-add-kubernetes-metadata/263615 "2021-02-08T14:36:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Francisco\_Peralta\_Gu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/francisco_peralta_gu/32/83575_2.png) [@Francisco\_Peralta\_Gu](https://discuss.elastic.co/u/Francisco_Peralta_Gu)\
**Post date:** [February 8, 2021, 2:36pm UTC](https://discuss.elastic.co/t/packetbeat-cannot-add-kubernetes-metadata/263615/1 "2021-02-08T14:36:36Z")

</div>

Hi.  
I am trying to configure packetbeat 1.10.1 in order to get kubernetes metadata in a kubernetes cluster v. 1.18.3 but I am not able to get it.

This is the configuration that I have applied:

```auto
       - add_cloud_metadata:
       - add_kubernetes_metadata:
           host: ${HOSTNAME}
           default_indexers.enabled: false
           default_matchers.enabled: false
           indexers:
             - ip_port:
           matchers:
           - field_format:
               format: '%{[ip]}:%{[port]}'

```

I also tried with the default indexers and matchers without any success.

The logs show the following information without any error:

```auto
  INFO [kubernetes] kubernetes/util.go:99 kubernetes: Using node ip-xx-xx-xx-xxx provided in the config {"libbeat.processor": "add_kubernetes_metadata"}.

```

Is there anything that I am missing in the setup, or any other consideration to take care of?

---

<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:** [March 8, 2021, 4:37pm UTC](https://discuss.elastic.co/t/packetbeat-cannot-add-kubernetes-metadata/263615/2 "2021-03-08T16:37:15Z")

</div>

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