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

Investigate how the UI handles users with user-base and cluster-owner roles #11598

Open
richard-cox opened this issue Aug 7, 2024 · 0 comments
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

richard-cox commented Aug 7, 2024

Epic: #10787

With a user who has the global user-base role and a specific cluster's cluster-owner role investigate what fails and degrade gracefully

  • This is NOT limited to but should include the following areas
  • Editing an existing RKE1 Cluster - all sections should render correctly
  • Editing an existing RKE2 Cluster - all sections should render correctly
  • Editing any of the hosted provider cluster
  • Cluster Context - Cluster Dashboard
  • Users & Authentication
  • Global Settings
  • User Avatar - Preferences, Accounts & API Keys

document additional permissions needed for the area's to render all content / all functionality works.

Consider doing #11598 and #11599 together

@richard-cox richard-cox added this to the v2.10.0 milestone Aug 7, 2024
@richard-cox richard-cox changed the title Handle users with permissions below the standard global role plus cluster owner Investigate how the UI handles users with user-base and cluster-owner roles Aug 7, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant