Merge pull request #56622 from lance5890/improve_cluster_restore_from_disater

add quorum guard instructions for etcd restoring from disaster

Author: ousleyp

modules/dr-restoring-cluster-state.adoc

@@ -301,6 +301,16 @@ Perform the following step only if you are using `OVNKubernetes` network plugin.
 ----
 $ oc delete node <non-recovery-controlplane-host-1> <non-recovery-controlplane-host-2>
 ----
+
+. Turn off the quorum guard by entering the following command:
++
+[source,terminal]
+----
+$ oc patch etcd/cluster --type=merge -p '{"spec": {"unsupportedConfigOverrides": {"useUnsupportedUnsafeNonHANonProductionUnstableEtcd": true}}}'
+----
++
+This command ensures that you can successfully re-create secrets and roll out the static pods.
+
 . Restart the Open Virtual Network (OVN) Kubernetes pods on all the hosts.
 +
 [NOTE]
@@ -553,6 +563,20 @@ $ oc patch etcd cluster -p='{"spec": {"forceRedeploymentReason": "recovery-'"$(
 +
 When the etcd cluster Operator performs a redeployment, the existing nodes are started with new pods similar to the initial bootstrap scale up.
 
+. Turn the quorum guard back on by entering the following command:
++
+[source,terminal]
+----
+$ oc patch etcd/cluster --type=merge -p '\{"spec": {"unsupportedConfigOverrides": null}}
+----
+
+. You can verify that the `unsupportedConfigOverrides` section is removed from the object by entering this command:
++
+[source,terminal]
+----
+$ oc get etcd/cluster -oyaml
+----
+
 . Verify all nodes are updated to the latest revision.
 +
 In a terminal that has access to the cluster as a `cluster-admin` user, run the following command: