Cherry-pick #24052 to 7.11: Add nodes to filebeat-kubernetes.yaml ClusterRole - fixes #24051 #24081
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.
Cherry-pick of PR #24052 to 7.11 branch. Original message:
What does this PR do?
Adds
nodes
to the fileabeat ClusterRole.Fixes #24051
Why is it important?
Filebeat will throw an error and be unable to list nodes without this.
Checklist
- [ ] 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 worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Deploy Filebeat from the latest manifest in the docs:
https://www.elastic.co/guide/en/beats/filebeat/7.11/running-on-kubernetes.html
curl -L -O https://raw.githubusercontent.com/elastic/beats/7.11/deploy/kubernetes/filebeat-kubernetes.yaml
Use the autodiscover config by doing the following:
# To enable hints based autodiscover, remove
filebeat.inputs
configuration and uncomment this:Filebeat starts up and is unable to list nodes:
This error goes away after adding
nodes
to the ClusterRole.Related issues
nodes
in the ClusterRole #24051Use cases
Screenshots
Logs
Logs without the change: