-
Sub-task
-
Resolution: Done
-
Major
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
-
-
VMMgmt - Train-31
- MulticlusterRoleAssignment will keep 1 ClusterPermission per cluster
- ClusterPermission will be labeled by one single label multiclusterroleassignment-uiĀ (or something)
- the mapping will be MulticlusterRoleAssignment.subjects to ClusterPermission.subjects
- roleBingdings in case targetNamespaces is present on MulticlusterRoleAssignment
- clusterRoleBingdings in case targetNamespaces is NOT present on MulticlusterRoleAssignment
- MulticlusterRoleAssignment will get clusters (for the clusterSet), will get already existing ClusterPermission for those clusters, otherwise new ClusterPermissions will be created
- subjects will be added accordingly (not checking duplication for the stage 1, me performed a tests for duplicated subjects for a ClusterPermission and there are no issues with it)
- check name fields are not duplicated
ClusterPermission limit is out of the scope for this task ACM-23681