fokifreaks.blogg.se - If you delete ivolume does the volume revert

#If you delete ivolume does the volume revert update#
#If you delete ivolume does the volume revert windows#

Check the status of the PV and it should now show "Available". Save the changes and close the editor.The lines to remove should look more or less like this: Remove all of the lines from (and including) "claimRef:" until the next tag with the same indentation level. In the editor, remove the entire "claimRef" section.Once that's finished, your PVC will get removed and the PV (and the disk it references!) will be left intact. Shutdown your pod/statefulset (and don't allow it to restart).Verify that the status of the PV is now Retain.

#If you delete ivolume does the volume revert windows#

Reconfigure your PV to set the reclaim policy to "Retain": (I'm doing this on Windows so you may need to handle the quotes differently depending on OS).

A new PVC can then be bound to it and all is well. The short version is that you just need reconfigure the PV to "Retain", allow the PVC to get deleted, then remove the previous claim from the PV. You won't need it, but if something goes wrong, the other answer here can then be used to re-create a disk from it. I ended up finding a simpler method to get everything straightened out that also preserved all of the extra Google/Kubernetes metadata and names.įirst, I would make a snapshot of your disk as suggested by another answer. My PVC said terminating because the pod referencing it was still running and the PV was configured with a retain policy of Deleted. It was with a statefulset on Google Cloud/GKE. I found myself in this same situation due to a careless mistake. Do not follow these instructions if you deleted the PV itself or the disk may be deleted!

#If you delete ivolume does the volume revert update#

Now just update your volume claim to target a specific volume, the last line of the yaml file: -Įdit: This only applies if you deleted the PVC and not the PV. Recreate the volume manually with the data from the disk:. Use the snapshot to create a disk: gcloud compute disks create name-of-disk -size=10 -source-snapshot=name-of-snapshot -type=pd-standard -zone=your-zoneĪt this point, stop the services using the volume and delete the volume and volume claim. In GKE console, go to Compute Engine -> Disks and find your volume there (use kubectl get pv | grep pvc-name) and create a snapshot of your volume. Once you are in the situation lke the OP, the first thing you want to do is to create a snapshot of your PersistentVolumes. The steps we took to remedy our broken state: Your PersistenVolumes will not be terminated while there is a pod, deployment or to be more specific - a PersistentVolumeClaim using it. We had the same problem and I will post our solution here in case somebody else has an issue like this. We have done so on GKE, not sure about AWS or Azure but I guess that they are similar It is, in fact, possible to save data from your PersistentVolume with Status: Terminating and RetainPolicy set to default (delete).