-
Notifications
You must be signed in to change notification settings - Fork 425
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
✨ Add aggregated role support #4933
✨ Add aggregated role support #4933
Conversation
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4933 +/- ##
=======================================
Coverage 62.19% 62.19%
=======================================
Files 201 201
Lines 16878 16878
=======================================
Hits 10497 10497
Misses 5591 5591
Partials 790 790 ☔ View full report in Codecov by Sentry. |
Both failures look like flakes: |
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.
I've been playing with this and it works great! Thanks!
/lgtm
/assign @mboersma
LGTM label has been added. Git tree hash: 40a2e7af67358900925e3df4e794f861fa7480f0
|
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.
/lgtm
/approve
Cool, thanks! I had to read up on Cluster Role aggregationRule
to understand. 👍🏻
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mboersma The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
CAPZ provider might need to have an ability to extend default set of RBAC, depending on deployment model or use cases, like with changes proposed in #4931. Splitting this out to test and improve on the changes separately.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
Release note: