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

RHDEVDOCS-2583 State that we do not remove PVC when undeploying

Browse Source
This commit is contained in:
rolfedh
2021-03-09 13:35:10 -05:00
parent 19d463e8f8
commit 2f43675e66
3 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
logging/cluster-logging-uninstall.adoc
View File

@@ -14,5 +14,6 @@ You can remove OpenShift Logging from your {product-title} cluster.
include::modules/cluster-logging-uninstall.adoc[leveloffset=+1]
.Additional resources
* xref:../storage/understanding-persistent-storage.adoc#reclaim-manual_understanding-persistent-storage[Reclaiming a persistent volume manually]

17
modules/cluster-logging-uninstall.adoc
View File

@@ -5,7 +5,10 @@
[id="cluster-logging-uninstall_{context}"]
= Uninstalling OpenShift Logging from {product-title}
You can stop log aggregation by deleting the `ClusterLogging` custom resource (CR). However, after deleting the CR there are other OpenShift Logging components that remain, which you can optionally remove.
You can stop log aggregation by deleting the `ClusterLogging` custom resource (CR). After deleting the CR, there are other OpenShift Logging components that remain, which you can optionally remove.
Deleting the `ClusterLogging` CR does not remove the persistent volume claims (PVCs). To preserve or delete the remaining PVCs, persistent volumes (PVs), and associated data, you must take further action.
.Prerequisites
@@ -43,7 +46,7 @@ To remove OpenShift Logging:
.. Click the Options menu {kebab} next to the Elasticsearch Operator and select *Uninstall Operator*.
. Optional: Remove the OpenShift Logging and Elasticsearch projects.
. Optional: Remove the OpenShift Logging and Elasticsearch projects.
.. Switch to the *Home* -> *Projects* page.
@@ -60,9 +63,17 @@ Do not delete the `openshift-operators-redhat` project if other global operators
.. Confirm the deletion by typing `openshift-operators-redhat` in the dialog box and click *Delete*.
. Optional: Remove any OpenShift Logging persistent volume claims (PVC):
. To keep the PVCs for reuse with other pods, keep the labels or PVC names that you need to reclaim the PVCs.
. Optional: If you do not want to keep the PVCs, you can delete them.
+
[WARNING]
====
Releasing or deleting PVCs can delete PVs and cause data loss.
====
.. Switch to the *Storage* -> *Persistent Volume Claims* page.
.. Click the Options menu {kebab} next to each PVC and select *Delete Persistent Volume Claim*.
.. If you want to recover storage space, you can delete the PVs.

1
modules/virt-importing-vm-cli.adoc
View File

@@ -142,7 +142,6 @@ EOF
* If the RHV VM migration mode is `Allow manual and automatic migration`, the default access mode is `ReadWriteMany`.
* If the RHV virtual disk access mode is `ReadOnly`, the default access mode is `ReadOnlyMany`.
* For all other settings, the default access mode is `ReadWriteOnce`.
<13> Specify the source VM disk ID, for example, `8181ecc1-5db8-4193-9c92-3ddab3be7b05`. You can obtain the disk ID by entering `\https://www.example.com/ovirt-engine/api/vms/vm23` in a web browser on the Manager machine and reviewing the VM details.
<14> Specify the target storage class.