Upgrading from IBM Cloud Pak for Data Version 4.8.x to a later 4.8 refresh

A Red Hat® OpenShift® Container Platform cluster administrator and instance administrator can work together to upgrade IBM Cloud Pak for Data from Version 4.8.x to a later 4.8 refresh.

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 Cloud Pak for Data Version 5.0 before Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to Version 5.0.

Before you begin

Before you upgrade Cloud Pak for Data:
  1. Review the information in the Planning section.

    Specifically, ensure that you review the System requirements. Your cluster must have sufficient resources.

  2. Ensure that you have a copy of script that defines the installation environment variables for your deployment.

    The script enables you to run most of the installation and upgrade commands without modifying them.

  3. Best practice Backup your Cloud Pak for Data installation before you upgrade.

    In the event of an unrecoverable failure, you can use the backup to recover your existing installation. For details, see Backing up and restoring Cloud Pak for Data.

  4. 4.8.5 or later If you are upgrading to Cloud Pak for Data Version 4.8.5 or later and your environment has scheduled backups, stop the scheduled upgrades.

Upgrade overview

The upgrade is broken up into the following phases:

1. Updating client workstations

Before you upgrade to a later 4.8 refresh, you must ensure that the workstation has the latest version of the cpd-cli and the olm-utils-v2 image.

User icon All administrators When icon Repeat as needed

What to do
  1. Complete Updating client workstations (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 2. Collecting required information.

2. Collecting required information

To successfully upgrade from IBM Cloud Pak for Data Version 4.8.x to a later 4.8 refresh, you have specific information about your environment.

User icon Cloud Pak for Data operations team When icon Repeat as needed

What to do
  1. Complete Determining which components to upgrade (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Complete Updating your environment variables script (Upgrading from Version 4.8.x to a later 4.8 refresh).
  3. Go to the appropriate section based on your environment:

3. Preparing to run upgrades in a restricted network

If you will run the IBM Cloud Pak for Data upgrade commands in a restricted network, you must prepare the client workstations before you move them behind your firewall.

User icon All administrators When icon Repeat as needed

What to do
  1. Complete Obtaining the olm-utils-v2 image before running IBM Cloud Pak for Data installation commands in a restricted network (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Complete Downloading CASE packages before running IBM Cloud Pak for Data upgrade commands in a restricted network (Upgrading from Version 4.8.x to a later 4.8 refresh).
  3. Go to the appropriate section based on your environment:

4. Preparing to run upgrades from a private container registry

User icon Different users need to complete the appropriate tasks.

When icon Some of these tasks can be completed once, but some of the tasks must be repeated for each user involved in the installation.

If you use a private container registry to host the IBM Cloud Pak for Data software images, you must mirror the updated images from the IBM Entitled Registry to the private container registry.

a. Mirroring images to the private container registry

If you mirrored the images for IBM Cloud Pak for Data Version 4.8.x to a private container registry, you must mirror the images for the 4.8 refresh that you want to install to the private container registry before you upgrade your installation.

User icon Registry administrator When icon Repeat as needed

What to do
  1. Complete the appropriate task for your environment in Mirroring images to a private container registry (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to b. Do users need to pull the olm-utils-v2 image from the private container registry?.
b. Do users need to pull the olm-utils-v2 image from the private container registry?

If the olm-utils-v2 image is available in the private container registry, you must update the cpd-cli to pull the image from the private container registry.

User icon All administrators When icon Repeat as needed

Options What to do
Your cluster is not in a restricted network and users can pull the image from the IBM Entitled Registry
  1. Go to 5. Upgrading shared cluster components.
Your cluster is not in a restricted network, but you want users to pull the image from the private container registry
  1. Complete Pulling the olm-utils-v2 image from the private container registry (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 5. Upgrading shared cluster components.
Your cluster is in a restricted network
  1. Complete Pulling the olm-utils-v2 image from the private container registry (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 5. Upgrading shared cluster components.

5. Upgrading shared cluster components

Before you upgrade IBM Cloud Pak for Data, you must upgrade the Certificate manager, License Service, and scheduling service.

User icon Cluster administrator When icon Repeat as needed

What to do
  1. Complete Upgrading shared cluster components (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 6. Preparing to upgrade an instance of Cloud Pak for Data.

6. Preparing to upgrade an instance of Cloud Pak for Data

If a user other than the cluster administrator will upgrade IBM Cloud Pak for Data, you must update the permissions on the projects that are associated with this instance of Cloud Pak for Data.

User icon Cluster administrator When icon Repeat as needed

Options What to do
The cluster administrator will upgrade the instance
  1. Go to 7. Upgrading an instance of Cloud Pak for Data.
Another user will upgrade the instance
  1. Complete Preparing to upgrade an instance of IBM Cloud Pak for Data (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 7. Upgrading an instance of Cloud Pak for Data.

7. Upgrading an instance of Cloud Pak for Data

To upgrade an instance of IBM Cloud Pak for Data, you must update the operators and operands (custom resources) that are associated with the instance.

User icon Instance administrator When icon Repeat as needed

a. Upgrading the IBM Cloud Pak foundational services for the instance

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.

What to do
  1. Complete Upgrading the IBM Cloud Pak foundational services (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to b. Upgrading Cloud Pak for Data.
b. Upgrading Cloud Pak for Data

After you upgrade the IBM Cloud Pak foundational services for the instance, you can upgrade the IBM Cloud Pak for Data control plane and services.

What to do
  1. Complete Upgrading IBM Cloud Pak for Data (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 8. Completing post-upgrade tasks.
c. Upgrading the cpdbr service

If you use the cpdbr service to back up and restore your IBM Cloud Pak for Data deployment on IBM Storage Fusion, NetApp Astra Control Center, or Portworx, you must upgrade the cpdbr service after you upgrade Cloud Pak for Data.

Options What to do
You don't use the cpdbr service
  1. Go to 8. Completing post-upgrade tasks.
You use the cpdbr service
  1. Complete Updating the cpdbr service (Upgrading from Version 4.8.x to a later 4.8 refresh).
  2. Go to 8. Completing post-upgrade tasks.

8. Completing post-upgrade tasks

After you upgrade Cloud Pak for Data, determine whether there are any additional tasks that you should complete to configure your Cloud Pak for Data cluster.

User icon Instance administrator When icon Repeat as needed

Options What to do
You upgraded the services when you upgraded the platform
  1. Complete the appropriate tasks for your environment in Setting up services after install or upgrade.
  2. If you want to use the resource specification injection (RSI) for the instance, complete Installing or updating the resource specification injection webhook for an instance of Cloud Pak for Data.
  3. 4.8.4 or later Starting in Version 4.8.4, JDBC driver upload is disabled by default. If you upgrade from Version 4.8.0, 4.8.1, 4.8.2, or 4.8.3 and you want to allow authorized users to upload JDBC driver files, you must complete Enabling users to upload JDBC drivers.
  4. 4.8.5 or later Starting in Version 4.8.5, the process for backing up Cloud Pak for Data changed. If you upgraded from one of the following versions, take a new backup of your installation using the 4.8.5 backup process and restart your scheduled backups:
    • 4.8.0
    • 4.8.1
    • 4.8.2
    • 4.8.3
    • 4.8.4
    For more information, see Backing up and restoring Cloud Pak for Data.
You didn't upgrade the services when you upgraded the platform
  1. Upgrade the services in the instance. For more information, see Services.
  2. Complete the appropriate tasks for your environment in Setting up services after install or upgrade.
  3. If you want to use the resource specification injection (RSI) for the instance, complete Installing or updating the resource specification injection webhook for an instance of Cloud Pak for Data.
  4. 4.8.4 or later Starting in Version 4.8.4, JDBC driver upload is disabled by default. If you upgrade from Version 4.8.0, 4.8.1, 4.8.2, or 4.8.3 and you want to allow authorized users to upload JDBC driver files, you must complete Enabling users to upload JDBC drivers.
  5. 4.8.5 or later Starting in Version 4.8.5, the process for backing up Cloud Pak for Data changed. If you upgraded from one of the following versions, take a new backup of your installation using the 4.8.5 backup process and restart your scheduled backups:
    • 4.8.0
    • 4.8.1
    • 4.8.2
    • 4.8.3
    • 4.8.4
    For more information, see Backing up and restoring Cloud Pak for Data.