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

Add data directories to kubernetes manifests #17429

Merged
merged 6 commits into from
Apr 6, 2020

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Apr 2, 2020

Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests. Filebeat is already mounting its data directory.

Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests.
@jsoriano jsoriano added review Metricbeat Metricbeat needs_backport PR is waiting to be backported to other branches. Auditbeat containers Related to containers use case Team:SIEM [zube]: In Review v7.7.0 Team:Platforms Label for the Integrations - Platforms team v7.6.3 labels Apr 2, 2020
@jsoriano jsoriano self-assigned this Apr 2, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@exekias
Copy link
Contributor

exekias commented Apr 2, 2020

This may worth a changelog?

@jsoriano
Copy link
Member Author

jsoriano commented Apr 3, 2020

This may worth a changelog?

Changelog entries added, and while adding them I saw that it didn't make sense to add a data directory to the metricbeat deployment because the instance can be run on any node, so I have reverted this part.

This would be ready for another look.

@jsoriano jsoriano requested a review from exekias April 3, 2020 11:54
@jsoriano jsoriano merged commit 257f0cc into elastic:master Apr 6, 2020
@jsoriano jsoriano deleted the auditbeat-data-directory-k8s branch April 6, 2020 08:09
jsoriano added a commit to jsoriano/beats that referenced this pull request Apr 6, 2020
Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests.

(cherry picked from commit 257f0cc)
@jsoriano jsoriano added v7.8.0 and removed needs_backport PR is waiting to be backported to other branches. labels Apr 6, 2020
jsoriano added a commit to jsoriano/beats that referenced this pull request Apr 6, 2020
Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests.

(cherry picked from commit 257f0cc)
jsoriano added a commit that referenced this pull request Apr 6, 2020
Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests.

(cherry picked from commit 257f0cc)
jsoriano added a commit that referenced this pull request Apr 6, 2020
Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests.

(cherry picked from commit 257f0cc)
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…#17509)

Mount data directories in Metricbeat and Auditbeat pods too. They were
defined in some places but not mounted.

For Auditbeat this is important so it doesn't have to rebuild its file
integrity database on each run. For Metricbeat I don't think it is so
important, but adding it just in case for consistency with the other
reference manifests.

(cherry picked from commit 168d8eb)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auditbeat containers Related to containers use case Metricbeat Metricbeat review Team:Platforms Label for the Integrations - Platforms team v7.6.3 v7.7.0 v7.8.0 [zube]: Done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants