filebeat: deploy k8s: use compression instead of gzip_experimental
#48079
+36
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
the docs will be updated on #47881
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the [(https://github.com/elastic/beats/blob/main/script/stresstest.sh) script to run them under stress conditions and race detector to verify their stability.stresstest.sh]./changelog/fragmentsusing the changelog tool.Disruptive User Impact
If users are using
gzip_experimental, they will need to change it tocompression: autoHow to test this PR locally
Use a filebeat with includes #47893
As this PR is just a config change, you can use the config from here directly on #47893
You can follow the sames steps as #47384. But you just need to check the gzip logs are ingested. No need to check again the edge-case when a container crashes.
Related issues
Use cases
Screenshots
Logs