In the restore documentation, we do not describe how to uncordon the nodes after rebooting them. Specifically we need to describe exactly how to login to the API server from the CLI potentially without access to the API VIP since during graceful shutdown we cordon all nodes

We need to decide what credential the user should be using, there is no guarantee that the oauth token from `oc login` will work which means we need a system:admin certificate credential.

Steps in the documentation should be:
1. Turn back on nodes

IF user is using the admin.kubeconfig from the cluster installation and the API VIP is up:
- User sets their KUBECONFIG env var to admin.kubeconfig path
- Use `oc adm uncordon <node>` for each node in the cluster

IF the user does not have access to their admin.kubeconfig credentials then they can follow the steps similar to https://access.redhat.com/solutions/6987229
- SSH to a control plane node
- copy localhost-recovery.kubeconfig to /root
- Use that kubeconfig to run `oc adm uncordon <node>` for each node in the cluster

At least back to docs for 4.12 which is where this documentation starts

Always