Merge pull request #14226 from rook/mergify/bp/release-1.14/pr-14190

doc: Update documentation for volume clone (backport #14190)
This commit is contained in:
Travis Nielsen authored and GitHub committed 2024-05-16 13:16:38 -06:00
commit 4b5c73ccd2
2 files changed
+20 -3

No files matched your search

@@ -66,7 +66,16 @@ The snapshot will be ready to restore to a new PVC when the `READYTOUSE` field o
In [pvc-restore](https://github.com/rook/rook/tree/master/deploy/examples/csi/rbd/pvc-restore.yaml),
`dataSource` should be the name of the `VolumeSnapshot` previously
created. The `dataSource` kind should be the `VolumeSnapshot`.
created. The `dataSource` kind should be the `VolumeSnapshot`. The `storageClassName`
can be any RBD storageclass.
Please Note:
* `provisioner` must be the same for both the Parent PVC and the restored PVC.
* The non-encrypted PVC cannot be restored to an encrypted one and vice-versa.
* encrypted -> encrypted (possible)
* non-encrypted -> non-encrypted (possible)
* encrypted -> non-encrypted (not possible)
* non-encrypted -> encrypted (not possible)
Create a new PVC from the snapshot
@@ -17,8 +17,16 @@ for more info.
In [pvc-clone](https://github.com/rook/rook/tree/master/deploy/examples/csi/rbd/pvc-clone.yaml),
`dataSource` should be the name of the `PVC` which is already created by RBD
CSI driver. The `dataSource` kind should be the `PersistentVolumeClaim` and also storageclass
should be same as the source `PVC`.
CSI driver. The `dataSource` kind should be the `PersistentVolumeClaim`.
The `storageClassName` can be any RBD storageclass (not necessarily same as Parent PVC)
Please note:
* `provisioner` must be the same for both the Parent PVC and the Clone PVC.
* The non-encrypted PVC cannot be cloned to an encrypted one and vice-versa.
* encrypted -> encrypted (possible)
* non-encrypted -> non-encrypted (possible)
* encrypted -> non-encrypted (not possible)
* non-encrypted -> encrypted (not possible)
Create a new PVC Clone from the PVC