mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
OCPBUGS#3813: Restarding and shutting down the cluster
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
bc9e4c5afa
commit
8a344f01f6
@@ -16,6 +16,9 @@ This document describes the process to gracefully shut down your cluster. You mi
|
||||
include::modules/graceful-shutdown.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
[id="additional-resources_restarting-restoring-cluster"]
|
||||
== Additional resources
|
||||
|
||||
* xref:../backup_and_restore/graceful-cluster-restart.adoc#graceful-restart-cluster[Restarting the cluster gracefully]
|
||||
|
||||
* 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]
|
||||
@@ -21,6 +21,14 @@ You can shut down a cluster until a year from the installation date and expect i
|
||||
[IMPORTANT]
|
||||
====
|
||||
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.
|
||||
|
||||
For example, the following conditions can cause the restarted cluster to malfunction:
|
||||
|
||||
* etcd data corruption during shutdown
|
||||
* Node failure due to hardware
|
||||
* Network connectivity issues
|
||||
|
||||
If your cluster fails to recover, follow the steps to restore to a previous cluster state.
|
||||
====
|
||||
|
||||
.Procedure
|
||||
|
||||
Reference in New Issue
Block a user