openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

BZ1856186 - Add manual reclaim proc

Browse Source
This commit is contained in:
Bob Furu
2020-08-12 17:29:36 -04:00
committed by openshift-cherrypick-robot
parent 2fbd697201
commit 00a526716e
2 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
modules/storage-persistent-storage-reclaim-manual.adoc Normal file
View File

@@ -0,0 +1,26 @@
// Module included in the following assemblies:
//
// * storage/understanding-persistent-storage.adoc
[id="reclaim-manual_{context}"]
= Reclaiming a PersistentVolume manually
When a PersistentVolumeClaim (PVC) is deleted, the PersistentVolume (PV) still exists and is considered "released". However, the PV is not yet available for another claim because the previous claimant's data remains on the volume.
.Procedure
To manually reclaim the PV as a cluster administrator:
. Delete the PV.
+
[source,terminal]
----
$ oc delete <pv-name>
----
+
The associated storage asset in the external infrastructure, such as an AWS EBS, GCE PD, Azure Disk, or Cinder volume, still exists after the PV is deleted.
. Clean up the data on the associated storage asset.
. Delete the associated storage asset. Alternately, to reuse the same storage asset, create a new PV with the storage asset definition.
The reclaimed PV is now available for use by another PVC.

2
storage/understanding-persistent-storage.adoc
View File

@@ -8,6 +8,8 @@ include::modules/storage-persistent-storage-overview.adoc[leveloffset=+1]
include::modules/storage-persistent-storage-lifecycle.adoc[leveloffset=+1]
include::modules/storage-persistent-storage-reclaim-manual.adoc[leveloffset=+2]
include::modules/storage-persistent-storage-reclaim.adoc[leveloffset=+2]
include::modules/storage-persistent-storage-pv.adoc[leveloffset=+1]