No Filebeat Daemonset (Deploying with Elastic Cloud on Kubernetes)

[directRoot]

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 (copied largely from here, except I added namespaces for the Kibana & ES refs)
2. kubectl get beat -o yaml

[michael.morello]

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