Upgrading from IBM Cloud Pak for Data Version 4.7 to Version 4.8

Services that cannot be upgraded to Version 4.8

Watson Knowledge Studio

The Watson Knowledge Studio service was deprecated in Version 4.7 and removed in Version 4.8.

Migrate your solutions to the Watson Discovery service, which has powerful custom natural language processing capabilities. You can import your existing Watson Knowledge Studio rules-based or machine learning models to Watson Discovery and apply them to your data as custom enrichments. You can also use the entity extractor feature in Watson Discovery to label and train new custom entity models.

For more information about migrating your solutions, see Migrating Knowledge Studio solutions in the Watson Discovery product documentation on IBM® Cloud.

After you migrate your solutions to Watson Discovery, uninstall Watson Knowledge Studio before you upgrade to Version 4.8. For more information, see Uninstalling Watson Knowledge Studio in the Version 4.7 documentation.

Before you begin

Upgrade overview

The upgrade is broken up into the following phases:

• 1. Updating your cluster
• 2. Updating client workstations
• 3. Collecting required information
• 4. Preparing to run upgrades in a restricted network
• 5. Preparing to run upgrades from a private container registry
• 6. Installing prerequisite software
• 7. Upgrading shared cluster components
• 8. Preparing to upgrade an instance of Cloud Pak for Data
• 9. Upgrading an instance of Cloud Pak for Data
• 10. Completing post-upgrade tasks

1. Updating your cluster

Before you upgrade IBM Cloud Pak for Data, ensure that your cluster is running a supported version of Red Hat OpenShift Container Platform and a supported version of your persistent storage.

Cluster administrator One-time setup

a. Are you running a supported version of Red Hat OpenShift Container Platform?

---

Supported versions of Red Hat OpenShift Container Platform

Cloud Pak for Data can be installed on the following versions of Red Hat OpenShift Container Platform:

• Version 4.12 or later fixes
• Version 4.14 or later fixes
• Version 4.15 or later fixes
• Version 4.16 or later fixes
• Version 4.17 or later fixes 4.8.9 or later
• Version 4.18.8 or later fixes 4.8.9 or later

---

Options	What to do
You are running a supported version of OpenShift	Go to b. Are you running a supported version of your persistent storage?
You are running an older version of OpenShift	Complete Upgrading Red Hat OpenShift Container Platform (Upgrading from Version 4.7 to Version 4.8). Go to b. Are you running a supported version of your persistent storage?

b. Are you running a supported version of your persistent storage?

---

Supported versions of persistent storage

Storage option	Version supported in 4.8	Upgrade notes
OpenShift Data Foundation	Version 4.12 Version 4.14 Version 4.15 Version 4.16 Version 4.17 4.8.9 or later Version 4.18 4.8.9 or later	Ensure that you are running a version that is compatible with the version of Red Hat OpenShift Container Platform that you are running on your cluster.
IBM Storage Fusion Data Foundation	Version 2.6.1 or later fixes Version 2.7.2 with the latest hotfix or later fixes Version 2.8.0 with the latest hotfix or later fixes	Ensure that you are running a version that is compatible with the version of Red Hat OpenShift Container Platform that you are running on your cluster.
IBM Storage Fusion Global Data Platform	Version 2.6.1 or later fixes Version 2.7.2 with the latest hotfix or later fixes Version 2.8.0 with the latest hotfix or later fixes	Ensure that you are running a version that is compatible with the version of Red Hat OpenShift Container Platform that you are running on your cluster.
IBM Storage Scale Container Native (with IBM Storage Scale Container Storage Interface)	Version 5.1.7 or later fixes, with CSI Version 2.9.0 or later fixes	Ensure that you are running a version that is compatible with the version of Red Hat OpenShift Container Platform that you are running on your cluster.
Portworx	Version 2.13.3 or later fixes Version 3.0.2 or later fixes	Ensure that you are running a version that is compatible with the version of Red Hat OpenShift Container Platform that you are running on your cluster.
NFS	Version 3 or 4	No action is required.
Amazon Elastic Block Store (EBS)	Not applicable	No action is required.
Amazon Elastic File System (EFS)	Not applicable	No action is required.
NetApp Trident	Version 22.4.0 or later fixes	No action is required.

---

Options	What to do
You are running a supported version of your persistent storage	Go to 2. Updating client workstations.
You have an older version of your persistent storage	Complete Upgrading your persistent storage (Upgrading from Version 4.7 to Version 4.8). Go to 2. Updating client workstations.

2. Updating client workstations

Before you can upgrade Cloud Pak for Data, you must ensure that the workstation has a supported version of the Cloud Pak for Data command-line interface and the OpenShift command-line interface.

All administrators Repeat as needed

3. Collecting required information

To successfully upgrade from IBM Cloud Pak for Data Version 4.7 to Version 4.8, you must have specific information about your environment.

Cloud Pak for Data operations team Repeat as needed

4. 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.

All administrators Repeat as needed

5. Preparing to run upgrades from a private container registry

Different users need to complete the appropriate tasks.

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.7 to a private container registry, you must mirror the images for Version 4.8 to the private container registry before you upgrade your installation.

Registry administrator Repeat as needed

What to do
Complete the appropriate task for your environment in Mirroring images to a private container registry (Upgrading from Version 4.7 to Version 4.8). 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.

All administrators 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	Go to 6. Installing prerequisite software.
Your cluster is not in a restricted network, but you want users to pull the image from the private container registry	Complete Pulling the olm-utils-v2 image from the private container registry (Upgrading from Version 4.7 to Version 4.8). Go to 6. Installing prerequisite software.
Your cluster is in a restricted network	Complete Pulling the olm-utils-v2 image from the private container registry (Upgrading from Version 4.7 to Version 4.8). Go to 6. Installing prerequisite software.

6. Installing prerequisite software

Several services have prerequisite software that must be upgraded or installed on the cluster by a cluster administrator.

Cluster administrator One-time setup

7. Upgrading shared cluster components

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

Cluster administrator Repeat as needed

8. 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.

Cluster administrator Repeat as needed

9. 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.

Instance administrator 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
Complete Upgrading the IBM Cloud Pak foundational services (Upgrading from Version 4.7 to Version 4.8). 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
Complete Upgrading IBM Cloud Pak for Data (Upgrading from Version 4.7 to Version 4.8). Go to c. Upgrading the cpdbr service.

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, you must upgrade the cpdbr service after you upgrade Cloud Pak for Data.

Options	What to do
You don't use the cpdbr service	Go to 10. Completing post-upgrade tasks.
You use the cpdbr service	Complete Updating the cpdbr service (Upgrading from Version 4.7 to Version 4.8). Go to 10. Completing post-upgrade tasks.

10. 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.

Instance administrator Repeat as needed