A Cloud Administrator is tasked with resolving a complex "Split-Brain" scenario in a Zonal Supervisor deployment following a storage outage in Zone-B.
Context:
The Supervisor spans Zone-A, Zone-B, and Zone-C. A storage array failure in Zone-B caused the Supervisor Control Plane VM in that zone to become isolated and read-only. The outage is now resolved, but the Supervisor status remains Warning. TKG clusters in Zone-B are unreachable.
Review the following diagnostic data from the Supervisor:
# kubectl get nodes -L topology.kubernetes.io/zone
NAME STATUS ROLES ZONE
42018c-supervisor-control-plane-0 Ready master Zone-A
42018c-supervisor-control-plane-1 NotReady master Zone-B
42018c-supervisor-control-plane-2 Ready master Zone-C
# kubectl get etcd -n kube-system
NAME STATUS HEALTH
etcd-0 Healthy true
etcd-1 Unhealthy false <-- Corresponds to Zone-B node
etcd-2 Healthy true
The administrator determines that the etcd member in Zone-B has diverged and cannot automatically rejoin the quorum.
What is the correct recovery procedure to restore full health to the Supervisor? (Choose 2.)