A VVF 9.0 administrator needs to enable vSphere Supervisor on a vSphere cluster to support Kubernetes workloads. The selected cluster consists of four ESXi hosts managed by vCenter 9.0. When attempting to configure the Supervisor through the vSphere Client, the option is greyed out. What is the most likely missing prerequisite?
Trap 1: The vCenter Server has not been joined to an Active Directory…
Active Directory integration is not a prerequisite to enable the vSphere Supervisor.
Trap 2: The ESXi hosts have not been licensed with VMware vSphere…
While licensing is required, a missing license typically restricts functionality post-deployment rather than greying out the wizard completely.
Trap 3: Shared VMFS datastores have not been mounted across all four hosts…
While storage is needed for persistent volumes later, Supervisor control plane VMs require specific storage policies rather than generic VMFS mounts to initiate.
- A
The vCenter Server has not been joined to an Active Directory domain for identity federation.
Why it fails: Active Directory integration is not a prerequisite to enable the vSphere Supervisor.
- B
NSX is not installed, or the cluster has not been prepared for NSX networking required by Workload Management.
Supervisor requires NSX networking for its management and workload networks; without NSX installed and the cluster prepared, Workload Management stays greyed out. This satisfies the stem's prerequisite constraint, since four ESXi hosts alone cannot enable Supervisor.
- C
The ESXi hosts have not been licensed with VMware vSphere Foundation keys.
Why it fails: While licensing is required, a missing license typically restricts functionality post-deployment rather than greying out the wizard completely.
- D
Shared VMFS datastores have not been mounted across all four hosts in the cluster.
Why it fails: While storage is needed for persistent volumes later, Supervisor control plane VMs require specific storage policies rather than generic VMFS mounts to initiate.