Upgrading shared cluster components (Upgrading from Version 5.2 to Version 5.4)

Before you upgrade IBM® Software Hub, you must upgrade the License Service and scheduling service.

Upgrade phase

Updating your client workstation
Collecting required information
Preparing to run an upgrade in a restricted network
Preparing to run an upgrade from a private container registry
Preparing the cluster
Preparing to upgrade an instance
Upgrading an instance
Setting up IBM Software Hub

Who needs to complete this task?

Cluster administrator A cluster administrator must complete this task.

Remember: If you gave another user the minimum role-based access control (RBAC) to install the scheduling service and you want that user to upgrade the scheduling service, you must complete Giving a user the minimum RBAC to install the scheduling service before you complete this task.

When do you need to complete this task?

One-time setup You must complete this task before you upgrade IBM Software Hub.

If you have multiple instances of IBM Software Hub on the cluster, it is strongly recommended that you upgrade the shared components to the same release as the latest version of IBM Software Hub that you plan to install on the cluster.

Before you begin

Best practice: You can run the commands in this task exactly as written using the installation environment variables. Ensure that you added the new environment variables from Updating your environment variables script.

In addition, ensure that you source the environment variables before you run the commands in this task.

About this task

License Service

If you're not sure which project the License Service is in, run the following command:

oc get deployment -A |  grep ibm-licensing-operator

Compare the project that is returned by the command to the projects that are in your installation environment variables script.

Scheduling service

If you're not sure whether the scheduling service is installed on the cluster, run the following command:

oc get scheduling -A

If the scheduling service is installed, the command returns information about the project where the scheduling service is installed and the version that is installed.
Ensure that the COMPONENTS variable in your environment variables script includes the scheduler component.
If the scheduling service is not installed, the command returns an empty response.

Procedure

Log the cpd-cli in to the Red Hat® OpenShift® Container Platform cluster:
```
${CPDM_OC_LOGIN}
```
Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.

Upgrade the License Service.

The command that you run depends on where the License Service is installed:

The License Service is in the ${PROJECT_LICENSE_SERVICE} project

cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--license_acceptance=true \
--licensing_ns=${PROJECT_LICENSE_SERVICE}

The License Service is in the ${PROJECT_CS_CONTROL} project

cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--license_acceptance=true \
--licensing_ns=${PROJECT_CS_CONTROL}

Wait for the cpd-cli to return the following message before proceeding to the next step:

[SUCCESS] ... The apply-cluster-components command ran successfully.

Confirm that the License Service pods are Running or Completed:
The License Service is in the ${PROJECT_LICENSE_SERVICE} project
```
 oc get pods --namespace=${PROJECT_LICENSE_SERVICE}
```
The License Service is in the ${PROJECT_CS_CONTROL} project
```
 oc get pods --namespace=${PROJECT_CS_CONTROL}
```

If the scheduling service is installed:

Upgrade the scheduling service:

cpd-cli manage apply-scheduler \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--license_acceptance=true \
--scheduler_ns=${PROJECT_SCHEDULING_SERVICE} \
--image_pull_prefix=${IMAGE_PULL_PREFIX} \
--image_pull_secret=${IMAGE_PULL_SECRET}

Confirm that the scheduling service pods are Running or Completed:
```
oc get pods --namespace=${PROJECT_SCHEDULING_SERVICE}
```

Install the Backup Restore Orchestration service for the scheduling service:

cpd-cli manage apply-br \
--license_acceptance=true \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--br_tool=oadp \
--oadp_ns=${OADP_PROJECT} \
--scheduler_ns=${PROJECT_SCHEDULING_SERVICE} \
--br_operator_ns=${PROJECT_SCHEDULING_BR_SVC} \
--image_pull_prefix=${IMAGE_PULL_PREFIX} \
--image_pull_secret=${IMAGE_PULL_SECRET}

What to do next

Now that you've upgraded the shared cluster components, you're ready to complete Preparing to upgrade an instance of IBM Software Hub (Upgrading from Version 5.2 to Version 5.4).