Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: Update documentation for volume clone #14190

Merged
merged 1 commit into from
May 16, 2024
Merged

doc: Update documentation for volume clone #14190

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion Documentation/Storage-Configuration/Ceph-CSI/ceph-csi-snapshot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
12 changes: 10 additions & 2 deletions Documentation/Storage-Configuration/Ceph-CSI/ceph-csi-volume-clone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
yati1998 marked this conversation as resolved.
Show resolved Hide resolved
* 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

Expand Down
Loading