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

Before you upgrade from IBM Cloud Pak® for Data Version 4.8 to IBM® Software Hub Version 5.2, you must upgrade the Certificate manager, License Service, and scheduling service.

Upgrade phase
  • You are not here. Updating your cluster
  • You are not here. Updating your client workstation
  • You are not here. Collecting required information
  • You are not here. Preparing to run an upgrade in a restricted network
  • You are not here. Preparing to run an upgrade from a private container registry
  • You are not here. Installing and upgrading prerequisite software
  • You are here icon. Updating the shared cluster components
  • You are not here. Preparing to upgrade an instance
  • You are not here. Upgrading an instance
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 from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.2.

If you have multiple instances of IBM Cloud Pak for Data 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.

For example, if you have two instances of IBM Cloud Pak for Data at Version 4.8 and you plan to upgrade one of the instances to IBM Software Hub Version 5.2.2, upgrade the shared cluster components to Version 5.2.2.

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

Certificate manager
If you are using the Red Hat® OpenShift® cert-manager, the IBM Cloud Pak foundational services Certificate manager upgrade will be skipped.
License Service
The location of the License Service depends on whether you installed Cloud Pak for Data with the private topology or whether you migrated to the private topology.
  • If you installed with the private topology, the License Service is in the project defined by the ${PROJECT_LICENSE_SERVICE} environment variable.
  • If you migrated to the private topology, the License Service is in the project defined by the ${PROJECT_CS_CONTROL} environment variable.

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

  1. 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.
  2. Upgrade the Certificate manager and 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} \
--license_acceptance=true \
--cert_manager_ns=${PROJECT_CERT_MANAGER} \
--licensing_ns=${PROJECT_LICENSE_SERVICE}
    The License Service is in the ${PROJECT_CS_CONTROL} project 
    cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--license_acceptance=true \
--cert_manager_ns=${PROJECT_CERT_MANAGER} \
--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.
  3. If you use the IBM Certificate manager, confirm that the Certificate manager pods in the ${PROJECT_CERT_MANAGER} project are Running or Completed: 
    oc get pods --namespace=${PROJECT_CERT_MANAGER}
  4. 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}
  5. If the scheduling service is installed, upgrade the scheduling service: 
    cpd-cli manage apply-scheduler \
--release=${VERSION} \
--license_acceptance=true \
--scheduler_ns=${PROJECT_SCHEDULING_SERVICE}
  6. If you upgraded the scheduling service, confirm that the scheduling service pods are Running or Completed: 
    oc get pods --namespace=${PROJECT_SCHEDULING_SERVICE}

What to do next

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