Merge pull request #92356 from lahinson/ocpbugs-50504-etcd-uncordon

[OCPBUGS-50504]: Update graceful shutdown docs

Author: lahinson

modules/graceful-restart.adoc

@@ -15,6 +15,29 @@ You can restart your cluster after it has been shut down gracefully.
 
 .Procedure
 
+. Turn on the control plane nodes.
++
+** If you are using the `admin.kubeconfig` from the cluster installation and the API virtual IP address (VIP) is up, complete the following steps:
++
+.. Set the `KUBECONFIG` environment variable to the `admin.kubeconfig` path.
+.. For each control plane node in the cluster, run the following command:
++
+[source,terminal]
+----
+$ oc adm uncordon <node>
+----
++
+** If you do not have access to your `admin.kubeconfig` credentials, complete the following steps:
++
+.. Use SSH to connect to a control plane node.
+.. Copy the `localhost-recovery.kubeconfig` file to the `/root` directory.
+.. Use that file to run the following command for each control plane node in the cluster:
++
+[source,terminal]
+----
+$ oc adm uncordon <node>
+----
+
 . Power on any cluster dependencies, such as external storage or an LDAP server.
 
 . Start all cluster machines.
@@ -157,4 +180,4 @@ ip-10-0-211-16.ec2.internal    Ready    control-plane,master   82m   v1.31.3
 ip-10-0-250-100.ec2.internal   Ready    worker                 69m   v1.31.3
 ----
 +
-If the cluster did not start properly, you might need to restore your cluster using an etcd backup.
+If the cluster did not start properly, you might need to restore your cluster using an etcd backup.