Enabling user permissions to clone data volumes across namespaces

By default, users cannot clone resources between namespaces. To enable cloning, a user with the cluster-admin role must create and bind a cluster role that grants the required permissions.

To enable a user to clone a virtual machine to another namespace, a user with the cluster-admin role must create a new cluster role. Bind this cluster role to a user to enable them to clone virtual machines to the destination namespace.

Creating RBAC resources for cloning data volumes

You can create a new cluster role that enables permissions for all actions for the datavolumes resource.

Prerequisites

You have installed the OpenShift CLI (oc).
You must have cluster admin privileges.

Note

If you are a non-admin user that is an administrator for both the source and target namespaces, you can create a Role instead of a ClusterRole where appropriate.

Procedure

Create a ClusterRole manifest:
yaml
```
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: <datavolume_cloner>
rules:
- apiGroups: ["cdi.kubevirt.io"]
  resources: ["datavolumes/source"]
  verbs: ["*"]
# ...
```
where:
<datavolume_cloner>
Specifies a unique name for the cluster role.
Create the cluster role in the cluster:
terminal
```
$ oc create -f <datavolume_cloner.yaml>
```
where:
<datavolume_cloner.yaml>
Specifies the file name of the ClusterRole manifest created in the previous step.
Create a RoleBinding manifest that applies to both the source and destination namespaces and references the cluster role created in the previous step.
yaml
```
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: <allow_clone_to_user>
  namespace: <source_namespace>
subjects:
- kind: ServiceAccount
  name: default
  namespace: <destination_namespace>
roleRef:
  kind: ClusterRole
  name: datavolume-cloner
  apiGroup: rbac.authorization.k8s.io
```
- metadata.name specifies a unique name for the role binding.
- metadata.namespace specifies the namespace for the source data volume.
- subjects.namespace specifies the namespace to which the data volume is cloned.
- roleRef.name specifies the name of the cluster role created in the previous step.
Create the role binding in the cluster:
terminal
```
$ oc create -f <datavolume_cloner.yaml>
```
where:
<datavolume_cloner.yaml>
Specifies the file name of the RoleBinding manifest created in the previous step.

Enabling user permissions to clone data volumes across namespaces¶

Creating RBAC resources for cloning data volumes¶

Enabling user permissions to clone data volumes across namespaces

Creating RBAC resources for cloning data volumes