Upgrading Platform Navigator (Component deployment interface)

This following procedures are for upgrading Platform Navigator. If you need information about installation, see Deploying Platform Navigator

Upgrading the Platform Navigator involves:

Updating the Platform Navigator operator using the Operator Lifecycle Manager (OLM).
Updating the Platform Navigator deployment by editing the Platform Navigator custom resource (CR).

These two operations can be configured to happen automatically, or they can be initiated manually.

Upgrading the operator

The OLM will attempt to upgrade an operator when a new version is available to the cluster.

Automatic approval - If the Platform Navigator operator subscription is set to Automatic approval, no action is required.
Manual approval - If the subscription is set to Manual approval, a Cluster Administrator must approve the InstallPlan created by OLM to upgrade the operator.
- You approve the InstallPlan on Operators > Installed Operators in the OpenShift console.
- The upgrade status under the Subscription tab displays as "Upgrading" until the user reviews and approves its Install Plan.
- After confirming approval on the Install Plan page, the subscription upgrade status changes to "Up to date".

An upgraded Platform Navigator operator may support new versions of the Platform Navigator.

Automatic upgrade - If your Platform Navigator CR spec.version is set to a channel, and the operator supports a newer version in that channel, your Platform Navigator deployment is automatically upgraded. To automatically upgrade to the latest version available, also set the spec.version value in the CR to latest. The spec.license.license value in the CR must be updated to complete the upgrade.
Manual upgrade - If your Platform Navigator spec.version is set to a specific version, upgrade your Platform Navigator by updating the spec.version and adding a valid spec.license.license in the Platform Navigator CR.
- You can identify what versions (for upgrade or downgrade) are available to a given instance of a Platform Navigator by looking at the status.versions.available section of a Platform Navigator CR. For additional details, see Operator channel versions for IBM Cloud Pak for Integration releases.
- For more information about specific licenses, see Licensing.

The EUS Platform Navigators require Red Hat OpenShift 4.6. Therefore, you must upgrade Red Hat OpenShift to version 4.6. See Updating a cluster between minor versions in the Red Hat OpenShift documentation.
After you have upgraded Red Hat OpenShift, navigate to the Installed Operators section in OpenShift and select the IBM Cloud Pak for Integration Platform Navigator operator.
Click the Subscription tab and change the channel to v4.1-eus. Result: OLM upgrades the operator to the latest EUS version. If manual approval is needed, a Cluster Administrator must approve the InstallPlan created by OLM to upgrade the operator.
Upgrading the operand:
- Automatic upgrade - If you have automatic upgrades switched on across Cloud Pak releases, where your CR spec.version is set to latest, the Platform Navigator deployment will attempt to upgrade automatically to the EUS version. You will need to add a valid spec.license.license in the Platform Navigator CR. You can confirm this by reviewing the reconciled version and status.conditions.
- Manual upgrade - If your Platform Navigator spec.version is set to a specific version, upgrade your Platform Navigator by updating the spec.version in the Platform Navigator CR to 2020.4.1-eus and adding a valid spec.license.license. For EUS use L-RJON-BUVMQX or L-RJON-BUVMYB. For more information about specific licenses, see Licensing.