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

Enable access to display cluster monitoring data for project members with "Viewer" permissions #11

Open
Tracked by #1338
donistz opened this issue Jan 29, 2021 · 0 comments
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@donistz
Copy link

donistz commented Jan 29, 2021

What would you like to be added:
Gardener project members assigned with "Viewer" role have to see the URL and credentials for Grafana.
Why is this needed:
At the moment Gardener project members assigned with "Viewer" role can see the cluster status but cannot see the monitoring data for the clusters they are responsible to monitor. Overall access to Grafana is only displayed at the moment for Gardener consumers (Owners and Admins of a project). There are no change activities possible for these users in the monitoring solution. This is a good reason to make the access to the monitoring solution accessible also to the project members assigned with the "Viewer" role in the project - they can be displayed with the URL and the secret for Grafana via the dashboard.
This is very important for large Kubernetes operation teams that are using Gardener where different level of responsibilities are organized. In such teams there are operators from the first level who are only responsible to monitor the status of the clusters and to look at the monitoring data to do evaluations and to report problems to the next level.

The best solution will be to implement an SSO solution for the monitoring tool and to also stop using static secrets for the authentication.

@donistz donistz added the kind/enhancement Enhancement, improvement, extension label Jan 29, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 22, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Mar 24, 2022
@wyb1 wyb1 added lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) and removed lifecycle/rotten Nobody worked on this for 12 months (final aging stage) labels Jun 3, 2022
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label May 3, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

3 participants