Error: VirtualMachineService LB does not yet have VIP assigned in VCF due to incorrect NSX Static Route
Article ID: 448751
Updated On:
Products
Issue/Introduction
Deployment of vSphere Kubernetes Service (VKS) clusters fails to complete. The process remains in a 'Creating' state because the Load Balancer VIP cannot be assigned when outbound connectivity from the Supervisor is black-holed.
VKS cluster provisioning fails to complete.
The following error is observed in vCenter: * LoadBalancerReady: VirtualMachineService LB does not yet have VIP assigned: VirtualMachineService LoadBalancer does not have any Ingresses.
Outbound traffic from the NSX Edge node reaches external interfaces but return traffic is not received.
Environment
Cause
The NSX Tier-0 Gateway has an incorrect Next Hop IP configured for the Default Static Route (0.0.0.0/0). This causes return traffic from external networks to be routed incorrectly or dropped, preventing the VirtualMachineService from completing the Load Balancer VIP assignment.
Resolution
Correct the Tier-0 Static Route configuration in NSX Manager:
- Log in to the NSX Manager UI.
- Navigate to Networking > Tier-0 Gateways.
- Locate and edit the Tier-0 Gateway used for the VKS environment.
- Select Routing > Static Routes.
- Identify the Default Route (0.0.0.0/0) entry.
- Update the Next Hop IP to the correct physical gateway address (e.g., ####).
- Save the configuration.
- Verify connectivity by performing a Traceflow or packet capture on the Edge node to ensure traffic reaches the correct gateway and receives a reply.
Feedback
