vSphere Kubernetes Service

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”

Published by

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…

VKS upgrade request is blocked when SystemChecksSucceeded is false because of a zero-disruption PodDisruptionBudget or a policy or service webhook blocker.

KB 433183: Fix VKS Cluster Upgrades Blocked by “SystemChecksSucceeded condition is not True”

Published by

TL;DR Broadcom KB 433183 describes a VKS 3.5 and later upgrade guardrail that blocks a version update when the cluster is likely to become stuck during rolling node replacement. The two broad causes are PodDisruptionBudgets with zero allowed disruptions and third-party admission webhooks that can prevent critical system pods from being created. Treat the condition … Explore: KB 433183: Fix VKS Cluster Upgrades Blocked by…