# No Filebeat Daemonset (Deploying with Elastic Cloud on Kubernetes)

**URL:** <https://discuss.elastic.co/t/no-filebeat-daemonset-deploying-with-elastic-cloud-on-kubernetes/378491>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 24, 2025, 4:05pm UTC](https://discuss.elastic.co/t/no-filebeat-daemonset-deploying-with-elastic-cloud-on-kubernetes/378491 "2025-05-24T16:05:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![directRoot](https://avatars.discourse-cdn.com/v4/letter/d/eb9ed0/32.png) [@directRoot](https://discuss.elastic.co/u/directRoot)\
**Post date:** [May 24, 2025, 4:05pm UTC](https://discuss.elastic.co/t/no-filebeat-daemonset-deploying-with-elastic-cloud-on-kubernetes/378491/1 "2025-05-24T16:05:12Z")

</div>

Hey all,

I have been deploying on K8s using the ECK operator, my ES & Kibana came up fine, but Filebeat for logs from each node is stubbornly refusing. No Daemonset is being created & a verbose description of the associated `beat` object shows the Kibana & ES associations as `Establised` 🤷

My node pool was pretty under powered initially, so I've thrown more resources at the problem (3x 4CPU, 8GB) but that didn't help.

I've also tried creating the Filebeat objects both _within_ the dedicated namespace I'm using for ECK and _outside_ of that in `default`, no dice.

Any advice on where to start debugging would be appreciated, I'm still pretty new to K8s 🙇

Thanks!

1. [Manifest](https://gist.github.com/DirectRoot/4fe91b860d7dde7e5bb0f11aea74d99a) (copied largely from [here](https://github.com/elastic/cloud-on-k8s/blob/main/config/recipes/beats/filebeat_autodiscover.yaml), except I added namespaces for the Kibana & ES refs)
2. [kubectl get beat -o yaml](https://gist.github.com/DirectRoot/c37d0686015572a3ad392c3ca1e67235)
3. 

![Screenshot 2025-05-24 at 5.02.59 PM](https://us1.discourse-cdn.com/elastic/original/3X/6/4/64e79e0782f1245ec1658e5205d006d176fd1173.png)

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [May 27, 2025, 6:04am UTC](https://discuss.elastic.co/t/no-filebeat-daemonset-deploying-with-elastic-cloud-on-kubernetes/378491/2 "2025-05-27T06:04:55Z")

</div>

You can maybe try `kubectl describe beat/filebeat` to check if something is not preventing the DaemonSet from being created.