Add how to for testing filebeat on kubernetes; minor docs adjustments#28670
Add how to for testing filebeat on kubernetes; minor docs adjustments#28670tetianakravchenko merged 2 commits intoelastic:masterfrom
Conversation
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
|
This pull request does not have a backport label. Could you fix it @tetianakravchenko? 🙏
NOTE: |
|
Pinging @elastic/integrations (Team:Integrations) |
| - logs_path: | ||
| logs_path: "/var/log/containers/" | ||
|
|
||
| # To enable hints based autodiscover, remove `filebeat.inputs` configuration and uncomment this: |
There was a problem hiding this comment.
Looks good overall! Maybe it worths adding some notes (bellow in the step-by-step part) about the differences of the 2 configs input+processor and provider. This is not so much part of this docs' scope but it would help to have the difference noted here too while dealing development and testing.
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
|
@ChrsMark @tetianakravchenko Was this on purpose not backported to 8.0? |
Signed-off-by: Tetiana Kravchenko tetiana.kravchenko@elastic.co
What does this PR do?
This PR adds instructions on how to test filebeat on Kubernetes locally , similar to #26643
Why is it important?
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs