From 6305046447b012b01b3b56cd3feb957cc3958639 Mon Sep 17 00:00:00 2001 From: Laura Hinson Date: Wed, 6 Aug 2025 13:21:28 -0400 Subject: [PATCH] Clarifying reqs to restore to a previous cluster state --- modules/dr-restoring-cluster-state.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/modules/dr-restoring-cluster-state.adoc b/modules/dr-restoring-cluster-state.adoc index 2becb747b1d1..045717f3fc5a 100644 --- a/modules/dr-restoring-cluster-state.adoc +++ b/modules/dr-restoring-cluster-state.adoc @@ -37,10 +37,11 @@ When you restore your cluster, you must use an etcd backup that was taken from t * A healthy control plane host to use as the recovery host. * You have SSH access to control plane hosts. * A backup directory containing both the `etcd` snapshot and the resources for the static pods, which were from the same backup. The file names in the directory must be in the following formats: `snapshot_.db` and `static_kuberesources_.tar.gz`. +* Nodes must be accessible or bootable. [IMPORTANT] ==== -For non-recovery control plane nodes, it is not required to establish SSH connectivity or to stop the static pods. You can delete and recreate other non-recovery, control plane machines, one by one. +For non-recovery control plane nodes, it is not required to establish SSH connectivity or to stop the static pods. You can delete and re-create other non-recovery, control plane machines, one by one. ==== .Procedure