This repository has been archived by the owner on May 16, 2023. It is now read-only.
[metricbeat] Enable events access to cluster role #254
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.
Metricbeat apparently needs access to events. I had to manually make this change to the clusterrole when installing the chart due to the following error:
Performing a resource sync err kubernetes api: Failure 403 events is forbidden: User "system:serviceaccount:monitoring:metricbeat-metricbeat" cannot list resource "events" in API group "" at the cluster scope for *v1.EventList
I haven't tried
filebeat
yet so I'm not sure this change is also required for it.${CHART}/tests/*.py
${CHART}/examples/*/test/goss.yaml