delete pvc1 (and the binding pv because deletionpolicy is set to Delete)
create pvc2 with volumesnapshot1, and it failed
Confirmed with neonsan team, this is expected. Deleting the PVC will delete all of things (including its snapshots), so the snapshot in neonsan has been removed as well.
Well, this might not meet k8s snapshot's purpose, which does not reply on the original pvc.
Possible solutions:
in neonsan, create snapshot with full-data, and it can not be removed when deleting the volume.
in neonsan or csi, when deleting volume, check if it has snapshots. If it has, do not delete the underlying volume (a fake delete).
csi-neonsan: v1.2.1
To recreate:
Delete
)Confirmed with neonsan team, this is expected. Deleting the PVC will delete all of things (including its snapshots), so the snapshot in neonsan has been removed as well.
Well, this might not meet k8s snapshot's purpose, which does not reply on the original pvc.
Possible solutions:
log: