Upgrading from v10.0.1.2 to v10.0.2.0 on VMware
You can upgrade API Connect on VMware from v10.0.1.2 or v10.0.1.2-ifix1 to v10.0.2.0
Before you begin
About this task
You can upgrade the Management subsystem, Developer Portal subsystem, and Analytics subsystem.
For the optional components API Connect Toolkit and API Connect Local Test Environment, you do not need to upgrade. For these components, install the new version of each after you upgrade the subsystems.
Important notes:
- When installing the new files, be sure to use the new
apicup
installer. - The upgrade order for subsystems is important. Upgrade the subsystems in the following order: (1) Management, (2) Portal, (3) Analytics, (4) Gateway. Management must be upgraded first. Gateway must be upgraded after Management because upgrading the Management service before the Gateway ensures that any new policies and capabilities will be available to a previously registered Gateway service.
- When you run the install, the program sends the compressed tar file, which contains the upgrade images, to all cluster members. The compressed tar file is about 2 GB, and transfer can take some time. When the install command exits, the compressed tar file has arrived at each member. The upgrade process is now underway, and might continue for some time depending on factors such as the size of your deployment, your network speed, etc.
- The
apicup subsys install
command automatically runsapicup health-check
prior to attempting the upgrade. An error is displayed if a problem is found that will prevent successful upgrade.
Note: Upon completion of each subsystem upgrade, reboot as required:
- For each subsystem, the upgrade process automatically runs
apicup health-check
upon completion of the upgrade. Whenapicup health-check
gives a message that reboot is required for a server, SSH onto that server and check the subsystem custom resource status:kubectl get <name_of_cr>
For example:
kubectl get managementCluster
If both
READY
isTrue
and theRECONCILED VERSION
shows the version you are upgrading to, then reboot that server. - During the upgrade, repeat this action for each subsystem when the message from
apicup subsys health-check
that says reboot is required for a server.