# Filebeat Helm chart run as non root

**URL:** <https://discuss.elastic.co/t/filebeat-helm-chart-run-as-non-root/325649>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 15, 2023, 4:31pm UTC](https://discuss.elastic.co/t/filebeat-helm-chart-run-as-non-root/325649 "2023-02-15T16:31:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DarthVader](https://avatars.discourse-cdn.com/v4/letter/d/a8b319/32.png) [@DarthVader](https://discuss.elastic.co/u/DarthVader)\
**Post date:** [February 15, 2023, 4:31pm UTC](https://discuss.elastic.co/t/filebeat-helm-chart-run-as-non-root/325649/1 "2023-02-15T16:31:17Z")

</div>

Hello,

I have been using Terraform to deploy the filebeat helm chart which currently runs successfully as root. Due to security policies I need to apply the pod security context "fsGroup" or anything similar that will enable the pod to run under filebeat user.

Currently, I am unable to set the security context on the pod level, because any modifications in my values.yaml file are going to the container level.

Any suggestions or ideas would be really appreciated.

Kind regards,  
Darth

---

<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 15, 2023, 6:31pm UTC](https://discuss.elastic.co/t/filebeat-helm-chart-run-as-non-root/325649/2 "2023-03-15T18:31:47Z")

</div>

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