Skip to content

Commit 0d8c2db

Browse files
committed
[OCPBUGS-50504]: Update graceful shutdown docs
1 parent 691bc13 commit 0d8c2db

File tree

1 file changed

+24
-1
lines changed

1 file changed

+24
-1
lines changed

modules/graceful-restart.adoc

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,29 @@ You can restart your cluster after it has been shut down gracefully.
1515
1616
.Procedure
1717

18+
. Turn on the control plane nodes.
19+
+
20+
** If you are using the `admin.kubeconfig` from the cluster installation and the API virtual IP address (VIP) is up, complete the following steps:
21+
+
22+
.. Set the `KUBECONFIG` environment variable to the `admin.kubeconfig` path.
23+
.. For each control plane node in the cluster, run the following command:
24+
+
25+
[source,terminal]
26+
----
27+
$ oc adm uncordon <node>
28+
----
29+
+
30+
** If you do not have access to your `admin.kubeconfig` credentials, complete the following steps:
31+
+
32+
.. Use SSH to connect to a control plane node.
33+
.. Copy the `localhost-recovery.kubeconfig` file to the `/root` directory.
34+
.. Use that file to run the following command for each control plane node in the cluster:
35+
+
36+
[source,terminal]
37+
----
38+
$ oc adm uncordon <node>
39+
----
40+
1841
. Power on any cluster dependencies, such as external storage or an LDAP server.
1942

2043
. Start all cluster machines.
@@ -157,4 +180,4 @@ ip-10-0-211-16.ec2.internal Ready control-plane,master 82m v1.31.3
157180
ip-10-0-250-100.ec2.internal Ready worker 69m v1.31.3
158181
----
159182
+
160-
If the cluster did not start properly, you might need to restore your cluster using an etcd backup.
183+
If the cluster did not start properly, you might need to restore your cluster using an etcd backup.

0 commit comments

Comments
 (0)