You can use the vSphere Client to deploy the NSX Manager to the vSphere cluster and use it with vSphere with Kubernetes.

To deploy the NSX Manager using the OVA file, perform the steps in this procedure.

For information about deploying the NSX Manager through the user interface or CLI, see the NSX-T Data Center Installation Guide.



  1. Locate the NSX-T Data Center OVA file on the VMware download portal.
    Either copy the download URL or download the OVA file.
  2. Right-click and select Deploy OVF template to start the installation wizard.
  3. Enter the download OVA URL or navigate to the OVA file.
  4. Enter a name for the NSX Manager virtual machine (VM).
  5. Select the vSphere cluster on which to deploy the NSX Manager.
  6. Select the NSX-T deployment size.
    The recommended minimum deployment size is Medium.
  7. Select the shared storage for deployment.
  8. Enable thin provisioning by selecting the Enable thin disk mode check box.
    The virtual disks are thick provisioned by default.
  9. Select the port group or destination network for the NSX Manager.
  10. Enter the system root, CLI admin, and audit passwords for the NSX Manager. Your passwords must comply with the password strength restrictions.
    • At least 12 characters.
    • At least one lower-case letter.
    • At least one upper-case letter.
    • At least one digit.
    • At least one special character.
    • At least five different characters.
    • Default password complexity rules are enforced by the Linux PAM module.
  11. Enter the hostname of the NSX Manager.
  12. Accept the default NSX Manager role for VM.
  13. Enter the default IPv4 gateway, management network IPv4, management network netmask, DNS server, domain search list, and NTP IP address.
  14. Enable SSH and allow root SSH login to the NSX Manager command line.
    By default, the SSH options are disabled for security reasons.
  15. Verify that your custom OVF template specification is accurate, and click Finish to initiate the installation.
  16. After the NSX Manager boots, log in to the CLI as admin and run the get interface eth0 command to verify that the IP address was applied as expected.
  17. Enter the get services command to verify that all the services are running.