When Kasten restores a PVC from a snapshot, it clones a PVC from the snapshot in the Kasten namespace. After the backend storage prepares the PV, the PVC in the Kasten namespace is deleted， then delete workload’s namespace pvc, finally, a new PVC is created in the workload's namespace and bound to the prepared PV.
This behavior disrupts a functional feature of the CSI interface, as detailed in this link (https://github.com/kubernetes-csi/external-provisioner/pull/399). In summary, the consequence is that from the perspective of the backend, all PVs appear to belong to the Kasten namespace. This can lead to unpredictable outcomes during backend cluster synchronization, mirroring, migration, and disaster recovery.
