starlingx/docs
Code Issues Proposed changes

Merge "Warn user to unmount volumes before uninstalling Rook Ceph"

Browse Source
This commit is contained in:
Zuul
2025-05-29 15:19:59 +00:00
committed by Gerrit Code Review
parent d172c93506 c422c69549
commit b40f908cd8
2 changed files with 17 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/shared/abbrevs.txt
View File

@@ -171,6 +171,7 @@
.. |PSPs| replace:: :abbr:`PSPs (Pod Security Policies)`
.. |PTP| replace:: :abbr:`PTP (Precision Time Protocol)`
.. |PTS| replace:: :abbr:`PTS (Primary Time Source)`
.. |PVs| replace:: :abbr:`PVs (Persistent Volumes)`
.. |PVC| replace:: :abbr:`PVC (Persistent Volume Claim)`
.. |PVCs| replace:: :abbr:`PVCs (Persistent Volume Claims)`
.. |PXE| replace:: :abbr:`PXE (Preboot Execution Environment)`

17
doc/source/storage/kubernetes/uninstall-rook-ceph-cbb046746782.rst
View File

@@ -9,9 +9,24 @@ Uninstall Rook Ceph
.. rubric:: |context|
To completely remove Rook Ceph you must remove the app and clear all the
To completely remove Rook Ceph, you must remove the application and clear all the
environment configurations to prevent an automatic reinstall.
.. note::
Before removing the Rook Ceph application(s), unmount all the persistent
volumes associated with the Rook Ceph cluster. This is achieved by removing
all the applications dependent on StorageClasses provided by the Rook Ceph
application. After removing the application(s), delete all |PVCs| and |PVs|
that were previously provided to the application(s).
If dependent application removal is not desired, then minimal cleanup is
needed. All pods with |PVCs| must be deleted, scaled down to zero, or
edited removing the |PVC| volume mounts. Otherwise, Rook Ceph application
removal will fail, volumes may hang, and nodes may require a restart. In
this case, a ``--force`` option is needed to remove the Rook Ceph
application and tear down the Ceph cluster.
.. rubric:: |proc|
#. Remove the application by running the script: