-
Sub-task
-
Resolution: Obsolete
-
Major
-
None
-
Product / Portfolio Work
-
False
-
-
-
VMMgmt - Train-31
It could be the case where information coming from ClusterPermission resources does not match from the existing resources on the console, like
apiVersion: rbac.open-cluster-management.io/v1alpha1
kind: ClusterPermission
metadata:
name: rb-view
namespace: local-cluster
spec:
roleBindings:
- namespace: default
roleRef:
name: kubevirt.io:view
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
subject:
name: UserX
apiGroup: rbac.authorization.k8s.io
kind: User
and
$ oc get user NAME UID FULL NAME IDENTITIES UserY 7d11e792-1bae-42ea-864f-f97b5cd57132
Currently application will behave like
