<p>The problem is that I need to modify the StorageClassName but it's not possible because there was a blank StorageClassName assigned.</p>
<p>This PVC is bound to a PV, so, if I delete the PVC to create a new one with the StorageClassName, the data that is in my AWS will be deleted?</p>

<p>You can recreate an existing PVC reusing the same PV with no data losses by using <a href="https://kubernetes.io/blog/2021/12/15/kubernetes-1-23-prevent-persistentvolume-leaks-when-deleting-out-of-order/" rel="nofollow noreferrer">reclaim policy</a>.</p>
<p>In case of Delete, the PV is deleted automatically when the PVC is removed, and the data on the PVC will also be lost.
In that case, it is more appropriate to use the “Retain” policy. With the “Retain” policy, if a user deletes a PersistentVolumeClaim, the corresponding PersistentVolume is not deleted. Instead, it is moved to the Released phase, where all of its data can be manually recovered.</p>
<p>Reclaim Policy: Used to tell the cluster what to do with the volume after releasing its claim. Current reclaim policies are:</p>
<ul>
<li>Retain — manual reclamation</li>
<li>Recycle — basic scrub (rm -rf/thevolume/*)</li>
<li>Delete — associated storage assets such as AWS EBS, GCE
PD, Azure Disk, or OpenStack Cinder volume is deleted</li>
</ul>
<p>NOTE: Extremely recommended to use Retain policy for PVCs that store critical data.</p>
<p>Here in this <a href="https://webera.blog/recreate-an-existing-pvc-in-a-new-namespace-but-reusing-the-same-pv-without-data-loss-2c7326c0035a" rel="nofollow noreferrer">blog</a> you have detailed steps to recreate a PVC in another name space similarly you can change the storage class.</p>
