An administrator is adding a vSphere Supervisor using VMware NSX classic to an existing VMware Cloud Foundation (VCF) cluster using Distributed Connectivity. When attempting to enable the vSphere…

Question

Options

• AThe WCPReady tag has not been been assigned to the NSX Edge Cluster.
• BThe NSX Edge transport nodes have been deployed as large.
• CvSphere Supervisor requires Central Connectivity.
• DAVI load balancing has not been enabled for the NSX Edge Cluster.

• A
  76% (19)
• B
  8% (2)
• C
  4% (1)
• D
  12% (3)

Explanation

A Comprehensive and Detailed Explanation: When enabling vSphere Supervisor with NSX Classic (using the traditional NSX-T Data Center networking stack rather than the newer NSX VPC mode), the vSphere Workload Management wizard filters the list of available NSX Edge Clusters to ensure they are explicitly designated for use with Kubernetes workloads. The "WCPReady" Tag Requirement: The primary mechanism vCenter uses to identify a valid, compatible Edge Cluster for Workload Management is a specific tag on the NSX Edge Cluster This tag must be WCPReady (case-sensitive). Symptoms: If this tag is missing--which often happens if the Edge Cluster was created manually in NSX Manager rather than through the SDDC Manager automation--the validation process will fail to find any usable clusters. This results in the specific error message: "No valid edge cluster for VDS [UUID]", or simply an empty list of compatible clusters in the wizard. Resolution: The administrator must log in to the NSX Manager, navigate to System > Fabric > Nodes > Edge Clusters, select the target cluster, and manually add the tag WCPReady (often with the scope "Created for", though the tag itself is the critical filter).

No community discussion yet for this question.