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.
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
- Review the information in the Planning section.
Specifically, ensure that you review the System requirements. Your cluster must have sufficient resources.
- 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.
- 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.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
- 2. Collecting required information
- 3. Preparing to run upgrades in a restricted network
- 4. Preparing to run upgrades from a private container registry
- 5. Upgrading shared cluster components
- 6. Preparing to upgrade an instance of Cloud Pak for Data
- 7. Upgrading an instance of Cloud Pak for Data
- 8. Completing post-upgrade tasks
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.
All administrators Repeat as needed
What to do |
---|
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.
Cloud Pak for Data operations team Repeat as needed
What to do |
---|
|
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.
All administrators Repeat as needed
What to do |
---|
|
4. 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.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.
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.8.x to a later 4.8 refresh).
- 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 thecpd-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 Your cluster is not in a restricted network, but you want users to pull the image from the private container registry Your cluster is in a restricted network
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.
Cluster administrator Repeat as needed
Options | What to do |
---|---|
The cluster administrator will upgrade the instance | |
Another user will upgrade the instance |
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.
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 - 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 - 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 thecpdbr
service after you upgrade Cloud Pak for Data.Options What to do You don't use the cpdbr
serviceYou use the cpdbr
service
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.
Instance administrator Repeat as needed
Options | What to do |
---|---|
You upgraded the services when you upgraded the platform |
|
You didn't upgrade the services when you upgraded the platform |
|