Supervisor cluster is not visible in the vSphere Client after a power outage

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• The Supervisor section in the vCenter UI is blank or missing.
  
  
  
  
• Supervisor control plane virtual machines are powered off, and the option to power them on in the vCenter inventory is greyed out.
• Pinging the Supervisor Virtual IP fails.
• This symptom may be seen post vCenter server has encountered a power outage.
• vCenter wcp logs shows below error 
  
  /var/log/vmware/wcp/wcpsvc.log

YYYY-MM-DD:T:HH:MM:SS info wcp [] reflector.go:158] "Unhandled Error" err="pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:243: Failed to watch contentsourcebindings: failed to list contentsourcebindings: the server is currently unable to handle the request"

YYYY-MM-DD:T:HH:MM:SS warning wcp [kubelib/retry.go:93] [opID=####-####-####-####] Request to apiserver failed. Err , Endpoint http://localhost:1080/external-cert/http1//6443/api/v1/namespaces/vmware-system-appplatform-operator-system/configmaps/vmware-system-psp-operator-features-config?timeout=2m0s. Will be retried.

Environment

• VMware vSphere Kubernetes Service (VKS)
• vCenter Server Appliance

Cause

Abrupt power loss can result in the Workload Control Plane service failing to initialize. The vSphere Client requires the WCP service to populate the Supervisor and Workload Management UI. If the service is not running, the cluster appears missing or inaccessible.

Resolution

A restart of the vCenter services re-initializes the WCP service and restores visibility to the Supervisor cluster.

1. Log in to the vCenter Server Appliance (VCSA) via SSH.
2. Check the status of all services to confirm if the wcp service is stopped or in an error state:
   
   service-control --status --all


3. Restart all vCenter services to ensure all dependencies are initialized:
   
   service-control --stop --all && service-control --start --all
   
   Note: This action results in a temporary disconnection of active vSphere Client sessions.
   
   
4. Log into the vSphere Client and navigate to Inventory > Workload Management to confirm the Supervisor cluster is visible and functional.