Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve README spell out RBAC requirements #70

Open
pebrc opened this issue Jan 11, 2022 · 1 comment
Open

Improve README spell out RBAC requirements #70

pebrc opened this issue Jan 11, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@pebrc
Copy link
Collaborator

pebrc commented Jan 11, 2022

We have not spelled out the specific RBAC requirements because of the assumption that the tool will always be run by admins. But that is certainly something we can improve in the README file for the diagnostic tool to enable restricted users to run it.

The user running the tool needs read access to all the resources listed here https://github.com/elastic/eck-diagnostics#information-collected-by-eck-diagnostics

The user also needs to be able to collect logs from all the Pods running Elastic Stack applications in the workload namespaces as well as all logs from all Pods in the namespace the operator runs in (typically elastic-system). This means get/list permissions on the pods/logs sub-resource.

If the user wants to extract stack diagnostics as well then additional permissions are needed to deploy and delete Pods into the workload namespaces and to exec into those Pods (pods/exec sub-resource) .

@pebrc pebrc added the documentation Improvements or additions to documentation label Jan 14, 2022
@Kattyi
Copy link

Kattyi commented Aug 12, 2024

Hello, any plans on documenting RBAC? Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants