# Regarding Filebeat and Kubernetes **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [November 28, 2018, 11:54am UTC](https://discuss.elastic.co/t/regarding-filebeat-and-kubernetes/158557 "2018-11-28T11:54:00Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\ **Post date:** [November 28, 2018, 11:54am UTC](https://discuss.elastic.co/t/regarding-filebeat-and-kubernetes/158557/1 "2018-11-28T11:54:00Z")
Hi, I'm weighing using a filebeat daemonset for shipping logs output by docker and written to disk on kubernetes nodes. Can I ask, is filebeat able to manage the logs on disk? That is, if the disk usage grows above a percentage remove the oldest logs? This is to account for possible outages downstream... Regards, D ---
**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\ **Post date:** [November 30, 2018, 8:36am UTC](https://discuss.elastic.co/t/regarding-filebeat-and-kubernetes/158557/2 "2018-11-30T08:36:17Z")
Filebeat is able to rotate its own log files. But rotating input files has to be done by an external tool right now. There is an open enhancement request on Github for this: [https://github.com/elastic/beats/issues/7633](https://github.com/elastic/beats/issues/7633) Feel free to add your use case to the issue, so when the feature is implemented your requirements can be taken account. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 28, 2018, 8:38am UTC](https://discuss.elastic.co/t/regarding-filebeat-and-kubernetes/158557/3 "2018-12-28T08:38:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.