You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metricbeat and Filebeat collect information from kubernetes, and for that @exekias prepared all the required resources you can see in this repository, Auditbeat in principle only collects information from the host, so a daemonset running privileged containers with its configuration in a configmap should be enough, yes. @mumoshu would you like to give a try? 🙂
It seems like we have ones for filebeat and metricbeat but for auditbeat in https://github.com/elastic/beats/tree/master/deploy/kubernetes
According to the explanation for running autitbeat in a docker container, probably we should just start by running auditbeat in a privileged container in pods managed by a daemonset.
The text was updated successfully, but these errors were encountered: