Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for adding a reference Kubernetes manifest for auditbeat #6733

Closed
mumoshu opened this issue Apr 3, 2018 · 2 comments
Closed

Proposal for adding a reference Kubernetes manifest for auditbeat #6733

mumoshu opened this issue Apr 3, 2018 · 2 comments
Assignees
Labels
containers Related to containers use case enhancement

Comments

@mumoshu
Copy link

mumoshu commented Apr 3, 2018

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.

@kvch kvch added containers Related to containers use case enhancement labels Apr 3, 2018
@jsoriano
Copy link
Member

jsoriano commented Apr 3, 2018

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? 🙂

@jsoriano
Copy link
Member

Added on #7642, @mumoshu it'd be great if you could take a look and give it a try 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Related to containers use case enhancement
Projects
None yet
Development

No branches or pull requests

4 participants