Upgrading NSX Application Platform

After deploying NSX Application Platform, you can upgrade it to a newer version.

Upgrade Requirements

Review the upgrade requirements and implement them in your environment to ensure a smooth upgrade with minimum downtime.

• Ensure that you meet the deployment requirements and prerequisites, especially that the NSX Application Platform version you plan to deploy is compatible with the NSX version that you are using for the deployment. Use the NSX Upgrade Matrix to assess the appropriate upgrade path for your environment to prevent upgrade errors.
• Before upgrading NSX, upgrade NSX Application Platform first to maintain compatibility and avoid pre-check failure preventing the upgrade.
• The upgrade process retains the form factor being used for the current platform deployment. If you deployed the platform using an Evaluation form factor and want to continue using an Evaluation form factor, but use a later platform version, you must delete your current NSX Application Platform deployment first. You then redeploy the platform using a later platform version.
• When you upgrade from NSX Application Platform 4.0.1 or 4.1.2 to 4.2 with a standard form factor to an advanced form factor, during the pre-upgrade verification, a notification indicates inadequate Kubernetes cluster resources. To continue with the upgrade, add worker nodes and repeat the pre-upgrade verification.
• Important:

  Beginning with NSX 3.2.3.1 release, the VMware-hosted NSX Application Platform registry and repository locations no longer support ChartMuseum-compatible private container registry, such as Harbor.

  If you are currently using an NSX version prior to 3.2.3.1, consider upgrading to NSX version 3.2.3.1 before attempting to upgrade your current NSX Application Platform deployment. Without the upgrade, users cannot access the repository, view new NSX Application Platform versions, and upgrade.

  If you are unable to access the public VMware-hosted NSX Application Platform registry and repository locations, work with your infrastructure administrator to upload the NSX Application Platform Helm chart and Docker images to your company's private Helm repository and Docker registry locations. Both privately-hosted locations must be accessible from the Kubernetes cluster and the NSX Manager appliance you are using for the NSX Application Platform deployment. If you need to continue using the ChartMuseum provided by Harbor, the Harbor version must be earlier than version 2.8.1. See Upload the NSX Application Platform Docker Images and Helm Charts to a Private Container Registry for details.