-
Sub-task
-
Resolution: Duplicate
-
Major
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
-
According to latest implementation from ClusterPermission CR ACM-19099, subjects has been included. UI is just working at "subject" level and "subjects" should be also considered. AccessControlManagementForm and AccessControlManagementTableHelper are affected by this
ClusterPermission example
apiVersion: rbac.open-cluster-management.io/v1alpha1
kind: ClusterPermission
metadata:
name: kubevirt-edit
namespace: jg-test-1
spec:
roleBindings:
- namespace: kubevirt-workspace-1
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubevirt.io:view
subjects:
- kind: User
name: Bob
apiGroup: rbac.authorization.k8s.io
- kind: User
name: Kike
apiGroup: rbac.authorization.k8s.io
- namespace: kubevirt-workspace-1
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubevirt.io:edit
subjects:
- kind: User
name: Bob
apiGroup: rbac.authorization.k8s.io
- kind: User
name: Kike
apiGroup: rbac.authorization.k8s.io
- namespace: kubevirt-workspace-2
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubevirt.io:view
subjects:
- kind: User
name: Bob
apiGroup: rbac.authorization.k8s.io
- kind: User
name: Kike
apiGroup: rbac.authorization.k8s.io
- namespace: kubevirt-workspace-2
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubevirt.io:edit
subjects:
- kind: User
name: Bob
apiGroup: rbac.authorization.k8s.io
- kind: User
name: Kike
apiGroup: rbac.authorization.k8s.io