Merge pull request #28863 from sgpinkus/patch-1
Update persistent-volumes.md
This commit is contained in:
@@ -131,7 +131,9 @@ The `Retain` reclaim policy allows for manual reclamation of the resource. When
|
|||||||
|
|
||||||
1. Delete the PersistentVolume. The associated storage asset in external infrastructure (such as an AWS EBS, GCE PD, Azure Disk, or Cinder volume) still exists after the PV is deleted.
|
1. Delete the PersistentVolume. The associated storage asset in external infrastructure (such as an AWS EBS, GCE PD, Azure Disk, or Cinder volume) still exists after the PV is deleted.
|
||||||
1. Manually clean up the data on the associated storage asset accordingly.
|
1. Manually clean up the data on the associated storage asset accordingly.
|
||||||
1. Manually delete the associated storage asset, or if you want to reuse the same storage asset, create a new PersistentVolume with the storage asset definition.
|
1. Manually delete the associated storage asset.
|
||||||
|
|
||||||
|
If you want to reuse the same storage asset, create a new PersistentVolume with the same storage asset definition.
|
||||||
|
|
||||||
#### Delete
|
#### Delete
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user