Skip to content

Commit 8e0bb02

Browse files
committed
OCPBUGS#3813: Move the note under prerequisite
1 parent a7149f0 commit 8e0bb02

File tree

2 files changed

+13
-15
lines changed

2 files changed

+13
-15
lines changed

backup_and_restore/graceful-cluster-shutdown.adoc

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,19 @@ This document describes the process to gracefully shut down your cluster. You mi
1111
== Prerequisites
1212

1313
* Take an xref:../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[etcd backup] prior to shutting down the cluster.
14+
+
15+
[IMPORTANT]
16+
====
17+
It is important to take an etcd backup before performing this procedure so that your cluster can be restored if you encounter any issues when restarting the cluster.
18+
19+
For example, the following conditions can cause the restarted cluster to malfunction:
20+
21+
* etcd data corruption during shutdown
22+
* Node failure due to hardware
23+
* Network connectivity issues
24+
25+
If your cluster fails to recover, follow the steps to xref:../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore to a previous cluster state].
26+
====
1427

1528
// Shutting down the cluster
1629
include::modules/graceful-shutdown.adoc[leveloffset=+1]
@@ -20,5 +33,3 @@ include::modules/graceful-shutdown.adoc[leveloffset=+1]
2033
== Additional resources
2134

2235
* xref:../backup_and_restore/graceful-cluster-restart.adoc#graceful-restart-cluster[Restarting the cluster gracefully]
23-
24-
* xref:../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[Restore to a previous cluster state]

modules/graceful-shutdown.adoc

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -17,19 +17,6 @@ You can shut down a cluster until a year from the installation date and expect i
1717

1818
* You have access to the cluster as a user with the `cluster-admin` role.
1919
* You have taken an etcd backup.
20-
+
21-
[IMPORTANT]
22-
====
23-
It is important to take an etcd backup before performing this procedure so that your cluster can be restored if you encounter any issues when restarting the cluster.
24-
25-
For example, the following conditions can cause the restarted cluster to malfunction:
26-
27-
* etcd data corruption during shutdown
28-
* Node failure due to hardware
29-
* Network connectivity issues
30-
31-
If your cluster fails to recover, follow the steps to restore to a previous cluster state.
32-
====
3320
3421
.Procedure
3522

0 commit comments

Comments
 (0)