Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

filebeat deployment in k8s failes to list nodes #703

Closed
bmilescu opened this issue Jul 1, 2020 · 0 comments · Fixed by #704
Closed

filebeat deployment in k8s failes to list nodes #703

bmilescu opened this issue Jul 1, 2020 · 0 comments · Fixed by #704
Labels
enhancement New feature or request filebeat

Comments

@bmilescu
Copy link
Contributor

bmilescu commented Jul 1, 2020

Chart version:
7.8.0
Kubernetes version:
v1.16.8
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AWS EKS
Helm Version:
v3.2.4

Missing permission to list nodes:
github.com/elastic/beats/libbeat/common/kubernetes/watcher.go:146: Failed to list *v1.Node: nodes "ip-x-x-x-x.us-west-2.compute.internal" is forbidden: User "system:serviceaccount:elastic:filebeat-filebeat" cannot list resource "nodes" in API group "" at the cluster scope
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request filebeat
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[filebeat] add permission to list nodes BuildingRobotics/helm-charts
2 participants
@jmlrt @bmilescu