TKGi-MC doesn't allow to select Network Resources when configuring TKGi with NSX Policy API

Products

• VMware Tanzu Kubernetes Grid Integrated Edition

Issue/Introduction

Configuring TKGi through Management Console with the following settings doesn't allow to select Network Resources.

• Container Networking Interface: NSX-T Data Center (Bring Your Own Topology) (BYOT)
• NSX Manager Details: Enable NSX-T Policy API

After selecting the "Network for TKGI Management Plane", no objects will be shown in the dropdown menu for the rest of the Network Resources: Pod IP Block ID, Node IP Block ID, T0 Router ID, Floating IP Pool ID.

On the browser > Developer Tools > Network, there will be HTTP 400 Bad Request responses to GET requests as below:

GET https://<tkgi-mc-fqdn>/api/inventory/nsx/t0router?policy=true

HTTP 400 Bad Request

message: error retrieving routers: [GET /transport-zones/{zone-id}][400] getTransportZoneBadRequest  &{RelatedAPIError:{Details: ErrorCode:9543 ErrorData:<nil> ErrorMessage:Cannot create HostSwitch {0} without HostSwitchMode and TransportZoneEndpoints. ModuleName:NsxSwitching service} RelatedErrors:[]}

In NSX Manager logs, similar errors can be found.

Environment

TKGi versions prior to 1.22.1

Cause

Software defect. TKGi-MC makes requests to the wrong NSX Manager API endpoints.

Resolution

Fix has been delivered in TKGi 1.22.1.

If a workaround is needed and upgrading to the fix release is not an option, please open a Support Request with Tanzu Support.