/usr/lib/vmware-wcp/decryptK8Pwd.py" gives an output, however we cannot SSH since the CP VMs do not exist.vSphere Kubernetes Service
The process to delete and clean up the supervisor got permanently stuck during the networking removal phase because a safety timer failed to work.
Ensure that a manual NSX cleanup completes or returns 0 resources to clean up:
Refer: VKS Supervisor Fails to Deactivate due to error "Cleanup requests to NSX Manager Failed"
Reach out to VMware by Broadcom Technical Support for assistance as the next steps involve editing the vCenter database directly.
If the Namespace resource pool and supervisor folder are still present in the inventory, reach out to Broadcom Support for cleaning up the stale resources.