# Possible to break down Filebeat Kubernetes Manifest File into smaller files? **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [June 4, 2024, 9:00pm UTC](https://discuss.elastic.co/t/possible-to-break-down-filebeat-kubernetes-manifest-file-into-smaller-files/360812 "2024-06-04T21:00:24Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![paolovalladolid](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@paolovalladolid](https://discuss.elastic.co/u/paolovalladolid)\ **Post date:** [October 11, 2024, 9:29pm UTC](https://discuss.elastic.co/t/possible-to-break-down-filebeat-kubernetes-manifest-file-into-smaller-files/360812/2 "2024-10-11T21:29:45Z")
I eventually found a solution to this scenario. I got another copy of the default filebeat-kubernetes.yaml manifest provided by Elastic here: [Run Filebeat on Kubernetes | Filebeat Reference [8.15] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html) If you deploy Filebeat as a DaemonSet with the above file, it will use a ServiceAccount, ClusterRole, ConfigMap, under the default `filebeat` name. So if you want to deploy a second Filebeat DaemonSet, you would use another manifest file, and edit ServiceAccount, ClusterRole, ConfigMap, etc. to use a name that is different than the name used by the first DaemonSet. So if you have say 3 software development teams running 3 different projects that are all deployed to the same Kubernetes node, you could set up 3 different manifest files, instead of configuring one monster size manifest file with settings for all 3 projects. More details here: [Filebeat DaemonSet on Kubernetes not shipping logs - Elastic Stack / Beats - Discuss the Elastic Stack](https://discuss.elastic.co/t/filebeat-daemonset-on-kubernetes-not-shipping-logs/368703) --- _[View the full topic](https://discuss.elastic.co/t/possible-to-break-down-filebeat-kubernetes-manifest-file-into-smaller-files/360812)._