Is it correct that when I delete a PV in Released status with "ReclaimPolicy: Retain" configuration, the CNS volume is also automatically deleted from infrastructure?
Here I would expect that after deleting such a PV the CNS volume in the infrastructure would not be automatically deleted.
Is this in line with official K8S guidelines?
The Retain reclaim policy allows for manual reclamation of the resource. When the PersistentVolumeClaim is deleted, the PersistentVolume still exists and the volume is considered "released". But it is not yet available for another claim because the previous claimant's data remains on the volume. An administrator can manually reclaim the volume with the following steps.
- Delete the PersistentVolume. The associated storage asset in external infrastructure still exists after the PV is deleted.
- Manually clean up the data on the associated storage asset accordingly.
- Manually delete the associated storage asset.
Other CSI drivers we have used so far behave as above.
Is it correct that when I delete a PV in Released status with "ReclaimPolicy: Retain" configuration, the CNS volume is also automatically deleted from infrastructure?
Here I would expect that after deleting such a PV the CNS volume in the infrastructure would not be automatically deleted.
Is this in line with official K8S guidelines?
Other CSI drivers we have used so far behave as above.