The purpose of this document is to show how to clone an image from an existing (file system or block) DV/PVC, to a target file system PV.
- You have a Kubernetes cluster up and running with CDI installed, source DV/PVC, and at least one available PersistentVolume to store the cloned disk image.
- The target PV is equal or larger in size than the source DV/PVC.
- When cloning from block to file system, content type must be kubevirt in both source and target, and host-assisted clone is used.
- When cloning across namespaces, the user must have the ability to create pods or have 'datavolumes/source' permission in the source namespace. You can give a user the appropriate permissions to a namespace by specifying RBAC rules.
Create the following DataVolume manifest clone-datavolume.yaml:
apiVersion: cdi.kubevirt.io/v1beta1
kind: DataVolume
metadata:
name: cloned-datavolume
spec:
source:
pvc:
namespace: source-ns
name: source-datavolume
storage: {}
Deploy the DataVolume manifest:
kubectl create -f clone-datavolume.yaml
By default, CDI will attempt the most efficient clone strategy possible. See Smart Cloning
For host-assisted cloning, two cloning pods, source and target, will be spawned and the image existed on the source DV/PVC, will be copied to the target DV.