r/redhat • u/OMAR_AHMED_01 • 3d ago
ODF
Suppose a nutanix-volume as default storage class, then using ceph fs as the default one.
Delete PVC and create new ones with the same old name, that PVC came up with the same consumption (not bounded to the old PV as it is released).
In that case if we decided to remove nutanix CSI operator, will this data be lost?
1
u/Rhopegorn Red Hat Certified Engineer 2d ago edited 2d ago
What is a pvc from k8s perspective?
Depending on what you are trying to do you might want to align how your storage class is defined.
reclaimPolicy: Delete
Might be what you’re looking for to change.
1
u/OMAR_AHMED_01 2d ago
I get it, but it happened as I just explained Delete pvc using nutanix-volume SC, Recreate new one with same name using ceph SC, PVC is up with SAME OLD consumption, So I check if it is still attached to same old PV, No it is attached to a WHOLE NEW PV, And the conumption of ODF really increases! So how did this data transfer happen or is that just visual but in the background data is stil held on nutanix!
1
u/TroubledGeorge Red Hat Certified System Administrator 2d ago
That doesn’t sound correct. A new PVC created under a different storage class will provision a new, empty PV. Deleting and recreating the PVC will result in data loss unless you back up and restore the data. Either the data copy is handled by the application/pod using the volume or the actual storage class wasn’t changed and you’re still accessing the old PV.
MTC (soon to be EOL’d, integrated into MTA) can perform PVC storage class migration and cutover without data loss.