Supervisor enablement is blocked when vLCM image compliance fails on ESXi hosts because of a noncompliant image, incompatible hosts, or legacy BIOS boot.

KB 393663: Fix Supervisor Deployment Stuck at “Installed and Started Kubernetes Node Agent on the ESXi Host”

TL;DR When vSphere Supervisor deployment stalls at Installed and Started Kubernetes Node Agent on the ESXi Host, do not treat the message itself as the root cause. For the failure documented in Broadcom KB 393663, the important evidence is repeated Apply Solution activity plus vCenter WCP log entries stating that the solution specification in the … Explore: KB 393663: Fix Supervisor Deployment Stuck at “Installed…