-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix Kubernetes cluster view when user is unable to scale #9867
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
Fix Kubernetes cluster view when user is unable to scale #9867
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #9867 +/- ##
==========================================
Coverage 15.08% 15.08%
- Complexity 11201 11203 +2
==========================================
Files 5404 5404
Lines 473424 473423 -1
Branches 60702 60168 -534
==========================================
+ Hits 71418 71428 +10
+ Misses 394059 394045 -14
- Partials 7947 7950 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
DaanHoogland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
|
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
) Co-authored-by: Henrique Sato <[email protected]>
Description
If a user does not have access to the
scaleKubernetesClusterAPI and tries to list Kubernetes clusters through the UI, an error is thrown. Therefore, it is not possible to list and create Kubernetes clusters due to this error, even if the user has permission for such actions.Since then, changes have been made so that this error no longer occurs and the user can list and manage Kubernetes clusters even if he doesn't have access to the
scaleKubernetesClusterAPI.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I created an account from a custom admin role that has the
scaleKubernetesClusterAPI asDENYand all other APIs asALLOW. Then, I logged into this account and was able to perform some basic operations like creating, listing and deleting a Kubernetes cluster.