This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Trimmed down permission for dashboard service account #2571
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.
What this PR does / why we need it:
This PR trims down the dashboard service account to the minimum possible per https://github.com/kubernetes/dashboard/wiki/Access-control#default-dashboard-privileges .
Current permission allow users to skip dashboard authentication and inherit cluster-admin priviledges nullifying the login process and RBAC resulting in an unsecure cluster.
With the proposed configuration, skipping login results in no permissions.
For development clusters, users can still reinstate previous permission manually granting cluster-admin permission to the dashboard service account.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #2425Special notes for your reviewer:
If applicable:
Release note: