From 76708d1d523019bf9352d4e34b355db77e9832e8 Mon Sep 17 00:00:00 2001 From: Alexander Trost Date: Tue, 14 May 2019 16:02:47 +0200 Subject: [PATCH] docs: added missing delete for new manifest structure This corrects the cleanup instructions to delete operator.yaml but also common.yaml to remove the reamining objects in one go. Signed-off-by: Alexander Trost --- Documentation/ceph-teardown.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/Documentation/ceph-teardown.md b/Documentation/ceph-teardown.md index 799268651..3bb77f6b8 100644 --- a/Documentation/ceph-teardown.md +++ b/Documentation/ceph-teardown.md @@ -27,7 +27,7 @@ kubectl delete storageclass rook-ceph-block kubectl delete -f kube-registry.yaml ``` -## Delete the Cluster CRD +## Delete the CephCluster CRD After those block and file resources have been cleaned up, you can then delete your Rook cluster. This is important to delete **before removing the Rook operator and agent or else resources may not be cleaned up properly**. ```console kubectl -n rook-ceph delete cephcluster rook-ceph @@ -38,15 +38,12 @@ Verify that the cluster CRD has been deleted before continuing to the next step. kubectl -n rook-ceph get cephcluster ``` -## Delete the Operator -This will begin the process of all cluster resources being cleaned up, after which you can delete the operator and related resources such as the agent and discover daemonsets with the following: +## Delete the Operator and related Resources +This will begin the process of the Rook Ceph operator and all other resources being cleaned up. +This includes related resources such as the agent and discover daemonsets with the following commands: ```console kubectl delete -f operator.yaml -``` - -Optionally remove the rook-ceph namespace if it is not in use by any other resources. -``` -kubectl delete namespace rook-ceph +kubectl delete -f common.yaml ``` ## Delete the data on hosts