How to Configure a vSphere Namespace to use a dedicated network subnet instead of the default network inherited from the Supervisor

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

This article describes configuring of a vSphere Namespace to use a dedicated network subnet instead of the default network inherited from the Supervisor.

Environment

VMware vSphere Kubernetes Service

Cause

The requirement is to use a dedicated network subnet instead of the default network inherited from the Supervisor.

Resolution

To assign a dedicated subnet to a vSphere namespace, utilize the "Override Supervisor Network Settings" feature by following one of below methods. 

Method 1: vSphere Client (UI)

1. Navigate to Workload Management > Namespaces.
2. Create a new namespace or select an existing one.
3. Under the Network section, select Override Supervisor Network Settings.
4. Refer to Create and Configure a vSphere Namespace on the Supervisor, to configure the following network settings for the namespace: 
5. Complete the configuration.

Method 2: vCenter dcli (Workaround for vCenter 9.0) In vCenter 9.0, when creating a new namespace by overriding the Supervisor network, the Tier 0 gateway is not seen in the vCenter UI. Use the dcli tool from the vCenter shell:

dcli> com vmware vcenter namespaces instances createv2 --namespace <namespace_name> --description "<Description>" --supervisor <Supervisor_ID> --namespace-network-network-nsx-tier0-gateway <T0_Gateway> --namespace-network-network-provider NSXT_CONTAINER_PLUGIN --namespace-network-network-routed-mode true --namespace-network-network-load-balancer-size SMALL --namespace-network-network-ingress-cidrs '[{"address": "X.X.X.X", "prefix":27}]' --namespace-network-network-subnet-prefix-length 28 --namespace-network-network-namespace-network-cidrs '[{"address": "X.X.X.X", "prefix": 27}]' --zones '[{"name":"<Zone_name>"}]'