From 0dbfc66498f44b2629f03652b5fe0443cb994383 Mon Sep 17 00:00:00 2001 From: subhamkrai Date: Wed, 2 Nov 2022 12:40:58 +0530 Subject: [PATCH] docs: update disaster recovery guide for webhook Since we moved to cert-manager for the webhook long time back, we just need to disable webhook instead of backing the whole webhook. And, after crs are restored we need to enable the webhook and all the resources will be created itself by the operator. Signed-off-by: subhamkrai --- .../Troubleshooting/disaster-recovery.md | 27 +++++-------------- 1 file changed, 6 insertions(+), 21 deletions(-) diff --git a/Documentation/Troubleshooting/disaster-recovery.md b/Documentation/Troubleshooting/disaster-recovery.md index ca56b35a9..5d094aa75 100644 --- a/Documentation/Troubleshooting/disaster-recovery.md +++ b/Documentation/Troubleshooting/disaster-recovery.md @@ -57,18 +57,10 @@ the CRs to their prior state without even necessarily suffering cluster downtime kubectl -n rook-ceph get configmap -o yaml > configmaps.yaml ``` -3. Back up and remove the `ValidatingWebhookConfiguration`. This is the resource which connects Rook custom resources to the - operator pod's validating webhook. Because the operator is unavailable, we must temporarily disable the valdiating webhook in - order to make changes. - - 1. Save the `ValidatingWebhookConfiguration` responsible for controlling Rook resources. (These are not namespaced - resources.) - - ```console - kubectl get ValidatingWebhookConfiguration rook-ceph-webhook -o yaml > rook-ceph-webhook.yaml - ``` - - 2. Delete the `ValidatingWebhookConfiguration`. +3. (Optional, if webhook is enabled) + Delete the `ValidatingWebhookConfiguration`. This is the resource which connects Rook custom resources + to the operator pod's validating webhook. Because the operator is unavailable, we must temporarily disable + the valdiating webhook in order to make changes. ```console kubectl delete ValidatingWebhookConfiguration rook-ceph-webhook @@ -144,20 +136,13 @@ the CRs to their prior state without even necessarily suffering cluster downtime 2. Remove the finalizer and confirm the CR is deleted (the underlying Ceph resources will be preserved) 3. Create the CR again -8. Restore the `ValidatingWebhookConfiguration`. - - ```console - kubectl create -f rook-ceph-webhook.yaml - ``` - -9. Scale up the operator +8. Scale up the operator ```console kubectl -n rook-ceph scale --replicas=1 deploy/rook-ceph-operator ``` - -10. Watch the operator log to confirm that the reconcile completes successfully. +9. Watch the operator log to confirm that the reconcile completes successfully. ```console kubectl -n rook-ceph logs -f deployment/rook-ceph-operator