# Kubernetes Metadata Not Being Add Via Filebeat

**URL:** <https://discuss.elastic.co/t/kubernetes-metadata-not-being-add-via-filebeat/187657>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 26, 2019, 7:17pm UTC](https://discuss.elastic.co/t/kubernetes-metadata-not-being-add-via-filebeat/187657 "2019-06-26T19:17:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tnemu](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@tnemu](https://discuss.elastic.co/u/tnemu)\
**Post date:** [June 26, 2019, 7:17pm UTC](https://discuss.elastic.co/t/kubernetes-metadata-not-being-add-via-filebeat/187657/1 "2019-06-26T19:17:00Z")

</div>

We recently moved to Filebeat 7.x however, we no longer get kubernetes metadata added to our events.

We are using Filebeat 7.1.1 and Filebeat 7.2.0. This worked just fine in Filebeat 6.3.2. Also using Kubernetes 1.12

Here is the filebeat.yml for the filebeat pods, which are running as a daemonset on each host.

We get the logs just fine, as well as the Cloud Metadata, but nothing for Kubernetes Metadata.

```
filebeat.inputs:
  - type: docker
    containers.ids:
     - "*"
    containers.path: "/data/docker/containers"

processors:
  - add_cloud_metadata:
  - add_kubernetes_metadata:
     in_cluster: true

output.logstash:
   hosts: ["logstash.me.admin.us-east-2.private.8labs.io:6045"]
   ssl:
    enabled: true

```

We also tried using the `container` input instead of the `docker` input in 7.2.0 but had the same issue.

---

<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:** [July 24, 2019, 7:17pm UTC](https://discuss.elastic.co/t/kubernetes-metadata-not-being-add-via-filebeat/187657/2 "2019-07-24T19:17:17Z")

</div>

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