# Filebeat on Kubernetes setup pipelines

**URL:** <https://discuss.elastic.co/t/filebeat-on-kubernetes-setup-pipelines/184430>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 5, 2019, 5:35pm UTC](https://discuss.elastic.co/t/filebeat-on-kubernetes-setup-pipelines/184430 "2019-06-05T17:35:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zx10r](https://avatars.discourse-cdn.com/v4/letter/z/a587f6/32.png) [@zx10r](https://discuss.elastic.co/u/zx10r)\
**Post date:** [June 5, 2019, 5:35pm UTC](https://discuss.elastic.co/t/filebeat-on-kubernetes-setup-pipelines/184430/1 "2019-06-05T17:35:55Z")

</div>

We are using filebeat in kubernetes to output to logstash. In order for the modules we use to be correctly parsed via pipelines and ingest nodes this needs to be enabled somehow but currently i see no way to pass it or enable it inside filebeat.yaml.

This is needed to pass the %{[@metadata][pipeline]}] to logstash so that it is parsed correctly inside elasticsearch. What is the correct way to do this or is it even possible?

---

<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 3, 2019, 5:35pm UTC](https://discuss.elastic.co/t/filebeat-on-kubernetes-setup-pipelines/184430/2 "2019-07-03T17:35:57Z")

</div>

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