Upgrading Enterprise PKS is a manual process. You must upgrade Enterprise PKS workload domains in your environment before upgrading NSX-T workload domains.
Upgrading Enterprise PKS to 1.7 is a multi-step process. This section includes links to the Pivotal documentation.
Procedure
- Upgrade Pivotal Operations Manager to version 2.7.16. See Upgrading Pivotal Platform.
Note: During the upgrade, you re-deploy the Operations Manager VM in vCenter and the old VM is powered off. Since vCenter Server does not allow two VMs with the same name, you can rename the old VM to something like
pivotal-ops-manager-old and keep the default name
pivotal-ops-manager for the new VM.
- Import the SSH key you created while upgrading Pivotal Operations Manager.
- Upgrade Enterprise PKS to 1.6. See Upgrading Enterprise PKS with NSX-T.
- Upgrade Pivotal Operations Manager to version 2.8.5. See Upgrading Pivotal Platform.
Note: During the upgrade, you re-deploy the Operations Manager VM in vCenter and the old VM is powered off. Since vCenter Server does not allow two VMs with the same name, you can rename the old VM to something like
pivotal-ops-manager-old and keep the default name
pivotal-ops-manager for the new VM.
- If you changed the SSH key after step 2, import the new key to VMware Cloud Foundation. See Import Operations Manager SSH Key to Cloud Foundation.
- Upgrade Enterprise PKS to 1.7. See Upgrading Enterprise PKS with NSX-T.
- Deploy the following client tools on Pivotal Operations Manager 1.7.
- If your workload domain includes Harbor Container Registry, upgrade the Harbor tile to version 1.10.1 build 7. See Upgrading VMware Harbor Registry.
What to do next
To login to Operations Manager after the upgrade, see
Log In to Operations Manager.
