Upgrading the IBM Cloud Pak foundational services (Upgrading from Version 4.7 to Version 4.8)

Important: IBM Cloud Pak for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

Before you can upgrade IBM Cloud Pak for Data, you must upgrade the IBM Cloud Pak foundational services that Cloud Pak for Data requires. Each instance of Cloud Pak for Data has its own instance of the IBM Cloud Pak foundational services.

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 prerequisite software
You are not here. Updating the shared cluster components
You are not here. Preparing to upgrade an instance of Cloud Pak for Data
You are here icon. Upgrading an instance of Cloud Pak for Data
Who needs to complete this task?

Instance administrator An instance administrator can complete this task.

When do you need to complete this task?

Repeat as needed If you have multiple instances of Cloud Pak for Data on the cluster, this task for each instance that you want to upgrade.

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

Run the setup-instance-topology command to upgrade the required IBM Cloud Pak foundational services software in the operators project.

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. Run the cpd-cli manage setup-instance-topology command to upgrade IBM Cloud Pak foundational services.
    Tip: Before you run this command against your cluster, you can preview the oc commands that this command will issue on your behalf by running the command with the --preview=true option.

    The oc commands are saved to the preview.sh file in the work directory.

    Instances without tethered projects 
    cpd-cli manage setup-instance-topology \
--release=${VERSION} \
--cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--license_acceptance=true \
--block_storage_class=${STG_CLASS_BLOCK}
    Instances with tethered projects 
    cpd-cli manage setup-instance-topology \
--release=${VERSION} \
--cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--additional_ns=${PROJECT_CPD_INSTANCE_TETHERED_LIST} \
--license_acceptance=true \
--block_storage_class=${STG_CLASS_BLOCK}

What to do next

Now that you've upgraded IBM Cloud Pak foundational services, you're ready to complete Upgrading IBM Cloud Pak for Data (Upgrading from Version 4.7 to Version 4.8).