sinful sparrow
Hi,
we have a customer currently using the vSphere CSI Driver in combination with Openshift 4.x, that would like to migrate to Trident CSI (ontap-nas / NFS) after our demo.
Do you guys have an idea, on the migration Path of the available PVCs (managed by vSphere CSI) to Trident managed PVCs in an automated / semi automated procedure?
Thanks and BR,
Philipp
sinful sparrow
Hi,
short update from our side. Our goal was it to have a lightweight solution without using a dedicated backup solution.
Here are our findings:
Korb
https://github.com/BeryJu/korb
Nice small tool that uses rsync for pvc migration and an temporary pod that mounts both the old and new pvc for data migration.
It even supports the following scenario:
Therefore you do not need to recreate the STS (VolumeClaimTemplate is immuteable) or update the Deployment.
Unfortunately the implemented hardcoded rsync configuration tries to fix the timestamps on the files that it copies over, which is not possible when using NFS. Permissions are taken over. As we can not deactivate the timestamp "recreation" under NFS it is not useable for our usecase.
PV Migrate
https://github.com/utkuozdemir/pv-migrate
Same as Korb, but with much more configuration options (e.g. rsync). Unfortunately misses the feature to automatically copy the data twice to persist PVC names accross workloads.
In worst case one can trigger it twice to receive the same functionality.
BR,
Philipp
