YYYY-MM-SSThh:mm:ssZ error wcp [apiserver/manager.go:###] [opID=######-######-######] timed out waiting for kube-apiserver-lb-svc service update. Err: context deadline exceededYYYY-MM-SSThh:mm:ssZ error wcp [kubelifecycle/controller.go:###] [opID=######-######-######] An error occurred fetching the virtual IP: Timed out waiting for LB service update. This operation is part of the cluster enablement and will be retried.. RetryingYYYY-MM-SSThh:mm:ssZ debug wcp [kubelifecycle/controller.go:###] [opID=######-######-######] Supervisor configuration retry.When NSX Avi Load Balancer is integrated with NSX Manager, the Supervisor enablement wizard prioritizes Avi as the default Load Balancer provider. This issue occurs if the Avi Load Balance is in degraded state (e.g., due to Service Engine failures or configuration or synchronization issues).
To resolve this issue, the load-balancing infrastructure must be brought back to a healthy state before re-attempting the Supervisor deployment:
Note: If you intend to use the native NSX-T Load Balancer, the Avi registration must be removed from the NSX Manager before initiating the supervisor deployment.