Migrating from NSX Management Proxy to Supervisor Management Proxy

Products

• VMware vSphere Kubernetes Service
• VMware Cloud Foundation

Issue/Introduction

In vSphere 9, The Supervisor Service NSX Management Proxy has been renamed to Supervisor Management Proxy which provides the following:

• connectivity to the NSX API's
• NSX metrics
• Remote endpoint for VKS clusters

Installation of the Supervisor Management Proxy on a Supervisor may lead to conflict if the NSX Management Proxy Supervisor Service is already running on that Supervisor. 

Environment

• nsx-management-proxy v0.1.1, v0.2.0, v0.2.1, v0.2.2
• supervisor-management-proxy v0.3.0

Resolution

It is required to migrate to the Supervisor Management Proxy for existing NSX Management Proxy users on a Supervisor.

If there is no existing VKS clusters with Antrea-NSX enabled then the following steps can be followed:

1. uninstall NSX Management Proxy.
2. install Supervisor Management Proxy.

The following workaround has been provided if there is an existing cluster with Antrea-NSX enabled. A K8s Load Balancer service named proxy-loadbalancer is present in the NSX Management Proxy as well as in the Supervisor Management Proxy. We need to ensure that External IP the of proxy-loadbalancer K8s Load Balancer service remains same after migration.

1. Note down External IP of the K8s Load Balancer service named proxy-loadbalancer of the NSX Management Proxy Supervisor Service. The External IP can be found in the vSphere Client UI at the following location:
   
   Supervisor Management > Supervisors > Click on the supervisor where the NSX Management Proxy is installed > Configure > Supervisor Services > Installed > NSX Management Proxy > Click on the Deployment Namespace-> Network > Services> External IPs
   
   
2. Install the Supervisor Management Proxy Supervisor Service, providing the data values according to the supervisor-management-proxy-data-values.yml. Make sure to fill the following sections:
   
   nsxManagers
nsxSvcLoadBalancerIP: <#.#.#.#> (This is the previously noted external IP)
   
   Note: It is expected that the Supervisor Management Proxy Pod may be in Crash Loop Back Off (CLBO) and will keep restarting. This happens when the Supervisor Management Proxy Pod is scheduled on the same Supervisor Control Plane Node on which the NSX Management Proxy Pod is running.  Also, it is expected that the K8s Load Balancer service named proxy-loadbalancer of Supervisor Management Proxy will not have an External IP at this point.
   
   
3. Uninstall the NSX Management Proxy Supervisor Service, then wait for a few minutes. After successfully uninstalling the NSX Management Proxy Supervisor Service, the Supervisor Management Proxy Pod will come into a running state(if it has not already) and the proxy-loadbalancer K8s Load Balancer service of the Supervisor Management Proxy will get the noted External IP. This can be verified using the vSphere Client UI at the following location:
   
   Supervisor Management > Supervisors > Click on supervisor where the Supervisor Management Proxy is installed > Configure > Supervisor Services > Installed > Supervisor Management Proxy> Click on the Deployment Namespace