-
Story
-
Resolution: Done
-
Normal
-
None
Value Statement
Implement new MulticlusterRoleAssignment CR for mapping, treating and dealing with ClusterPermission CR
See related DDRs and documents:
- ACM-DDR-056: MulticlusterRoleAssignment CR
- RBAC rethinking in ACM
- How to: Create ClusterPermissions
- ACM RBAC Separation of concerns
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- blocks
-
-
- Closed
-
- depends on
-
ACM-23312 ClusterPermission reports success status even when ManfestWork fails
-
- Backlog
-
- is cloned by
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is related to
-
ACM-22086 Revisit the approach to how users expect kubevirt roles to be present on the hub cluster in ACM 2.15
-
- Closed
-
- relates to
-
-
- Closed
-