anchor.diff:  +
   If the status is `Pending`, or the output lists more than one running etcd pod, wait a few minutes and check again.
   
  +.. Repeat this step for each lost control plane host that is not the recovery host.
  +
   . In a separate terminal window, log in to the cluster as a user with the `cluster-admin` role by using the following command:
   +
   [source,terminal]
  
positive.code: [id="dr-scenario-2-restoring-cluster-state_{context}"]
  = Restoring to a previous cluster state
  
  You can use a saved etcd backup to restore back to a previous cluster state. You use the etcd backup to restore a single control plane host. Then the etcd cluster Operator handles scaling to the remaining control plane hosts.
  
  [IMPORTANT]
  ====
  
negative.code: +
  In a terminal that has access to the cluster as a `cluster-admin` user, run the following commands.
  
  .. Force a new rollout for the Kubernetes API server:
  +
  [source,terminal]
  ----
  