VKS Deployment Fails to Detect Tier-0 Gateway During Network Configuration with, "Unable to infer NSX Tier 0 Gateway for VDS <VDS UUID> and Edge Cluster <UUID>. No known Tier 0 Gateways were found in Overlay Transport Zone <UUID>"
book
Article ID: 419728
calendar_today
Updated On:
Products
VMware vSphere Kubernetes Service
Issue/Introduction
When deploying the VKS service, the Tier-0 Gateway does not appear during the network configuration step. Continuing with the deployment results in the following message:
Unable to infer NSX Tier 0 Gateway for VDS <VDS UUID> and Edge Cluster <UUID>. No known Tier 0 Gateways were found in Overlay Transport Zone <UUID>
A Tier-0 Gateway is present on the NSX Local Manager and was originally created from a Global Manager environment.
The Edge Cluster referenced in the error exists, and its Tier-0 and Tier-1 Gateways (if applicable) are visible.
Edge nodes in the cluster are correctly associated with the Overlay Transport Zone mentioned in the error.
The production environment is functioning normally; the issue occurs during a new VKS deployment attempt.
Environment
VMware vSphere Supervisor VMware NSX 4.x.x
Cause
VKS (WCP) deployment requires Tier-0 Gateways that are locally managed. In environments where NSX Federation is used and Tier-0 Gateways are created from Global Manager, the VKS workflow cannot retrieve the required Tier-0 information during deployment.
Resolution
VKS/WCP deployment is not supported when using NSX Federation for Tier-0 Gateway management.
To proceed with deployment, create the required Tier-0 Gateway directly on the NSX Local Manager.
For design considerations or assistance with federated environments, please consult your Professional Services representative.