Provide RBAC rules for virtualmachines-apb about kubevirt-apb HOT 5 CLOSED

i dont think adding rbac rules will do the trick, as the crd is created within the apb

from kubevirt-apb.

@karmab are you saying that the CRD, the API for the VM, doesn't exist until the vm is created so we can't create any rules for it because k8s doesn't what the API we're talking about?

Can we create the CRD here?

from kubevirt-apb.

actually what i meant is that the apb would be creating a vm object (crd) living in a different namespace than the one it s currently deployed, for me this didnt work, but maybe i m wrong ( and it has to do with the next section ).

but it's worse, because even if the apb can create objects in the destination namespace, we would get errors like the following, though the user does belong to the indicated namespace

[jmayer@master01 ~]$ oc get vm
Error from server (Forbidden): virtualmachines.kubevirt.io is forbidden: User "jmayer" cannot list virtualmachines.kubevirt.io in the namespace "woodstock": User "jmayer" cannot list virtualmachines.kubevirt.io in project "woodstock"

from kubevirt-apb.

@rthallisey is this still relevant? or did it become obsolete with the latest changes in kubevirt roles mgmt?

from kubevirt-apb.

@nellyc closed. Aggregated roles were added.

from kubevirt-apb.