Upgrading from IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2
Starting in Version 5.1, the control plane is called IBM Software Hub. You can upgrade from IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2.
A Red Hat® OpenShift® Container Platform cluster administrator and instance administrator can work together to upgrade IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2.
Upgrading to Version 5.2.0 is not recommended because you must manually apply fixes after you upgrade to 5.2.0.
The fixes are included in Version 5.2.1 and later.
Before you begin
- Review the information in the Planning
section.
Specifically, ensure that you review the System requirements. Your cluster must have sufficient resources.
- Review the information in Planning an upgrade.
- 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
IBM 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 IBM Cloud Pak for Data in the IBM Cloud Pak for Data Version 5.0 documentation.
Services that are not available on Version 5.2
- Watson Machine Learning Accelerator
- Watson Machine Learning Accelerator is not available on IBM Software Hub Version 5.2.
If you use Watson Machine Learning, you no longer need Watson Machine Learning Accelerator to train deep learning experiments.
If Watson Machine Learning Accelerator is installed on IBM Cloud Pak for Data Version 5.0:- Back up any model definitions that you plan on recreating in Watson Machine Learning.
- Uninstall the Watson Machine Learning Accelerator service.
For more information, see Preparing to upgrade Watson Machine Learning.
Services that cannot be upgraded from Version 5.0 to Version 5.2
- Match 360
- You cannot directly upgrade the Match 360
service from Version 5.0.x to Version 5.2. If you have this service on your
environment, you must:
- Upgrade from Cloud Pak for Data Version 5.0.x to IBM Software Hub Version 5.1.3.
- Upgrade Match 360 to Version 5.1.3.
- Migrate your database from FoundationDB to Neo4j.
- Upgrade from Version 5.1.3 to Version 5.2.
- watsonx Code Assistant™ for Z Code Explanation
- watsonx Code Assistant for Z Code Explanation cannot be upgraded
from Version 5.0 to Version 5.2.
If you want to upgrade to IBM Software Hub Version 5.2, uninstall watsonx Code Assistant for Z Code Explanation before you upgrade to IBM Software Hub Version 5.2.
You can re-install watsonx Code Assistant for Z Code Explanation after you upgrade to watsonx Code Assistant for Z Code Explanation.
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 prerequisite software
- 6. Upgrading shared cluster components
- 7. Preparing to upgrade an instance of IBM Cloud Pak for Data
- 8. Upgrading an instance of IBM Cloud Pak for Data
- 9. Installing or upgrading the privileged monitoring service
- 10. Installing or upgrading the admission controller webhook
- 11. Completing post-upgrade tasks
1. Updating client workstations
Before you
upgrade to IBM Software Hub Version 5.2, you must ensure that the workstation has the latest version of the
cpd-cli and the olm-utils-v3
image.
All administrators
Repeat as needed
| What to do |
|---|
2. Collecting required information
To successfully upgrade from IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2, you must have specific information about your environment.
Operations team
Repeat as needed
| What to do |
|---|
|
3. Preparing to run upgrades in a restricted network
If you will run the 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 Software Hub 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 5.0 to a private container registry, you must mirror the images for IBM Software Hub 5.2 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 5.0 to Version 5.2).
- Go to b. Do users need to pull the olm-utils-v3 image from the private container registry?.
- b. Do users need to pull the
olm-utils-v3image from the private container registry? -
If the
olm-utils-v3image is available in the private container registry, you must update thecpd-clito 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
5. Upgrading prerequisite software
Several services have prerequisite software that must be upgraded by a cluster administrator.
Cluster administrator
Most of the tasks can be completed once, but some of the tasks must be
repeated if you have multiple instances of the service on the cluster.
Services with a dependency on prerequisite software
| Prerequisite software | Services with this prerequisite | Upgrade this software if... |
|---|---|---|
| Node Feature Discovery Operator |
An asterisk (*) indicates that the service requires GPU in some situations.
|
You upgraded Red Hat
OpenShift Container Platform and the operator is installed with
installPlanApproval: Manual. |
| NVIDIA GPU Operator |
An asterisk (*) indicates that the service requires GPU in some situations.
|
The version of the operator on your cluster has reached the end of support. For details, see NVIDIA GPU Operator Life Cycle in the NVIDIA GPU Operator documentation. |
| Red Hat OpenShift AI |
An asterisk (*) indicates that the service requires Red Hat OpenShift AI in some situations.
|
You must upgrade this software when you upgrade from IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.1. |
| Multicloud Object Gateway |
|
You must upgrade this software if you upgrade Red Hat OpenShift Container Platform. |
| Red Hat OpenShift Serverless Knative Eventing |
|
If you plan to upgrade an instance of Cloud Pak for Data that includes watsonx Assistant or watsonx Orchestrate, you must upgrade this software if:
|
| Options | What to do |
|---|---|
| The instance that you are upgrading does not include any services with a dependency on prerequisite software | |
| You are upgrading services with a dependency on prerequisite software |
7. Preparing to upgrade an instance of IBM Cloud Pak for Data
Before you upgrade an instance of IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2, a cluster administrator must prepare the instance for upgrade.
Cluster administrator
Repeat as needed
- a. Checking the health of your cluster
- The IBM Software Hub
command-line interface includes commands that you can use the validate the health of your cluster
before you upgrade from IBM Cloud Pak for Data
Version 5.0 to IBM Software Hub Version 5.2. If you do not validate
the health of your cluster before you upgrade to IBM Software Hub Version 5.2, you
might encounter issues during the upgrade.
What to do - b. Do you need to reauthorize the instance administrator?
-
If you gave an instance administrator the minimum role-based access control (RBAC) to install IBM Cloud Pak for Data Version 5.0 software, you must update the roles that are assigned to the user so that the user has sufficient privileges to upgrade the instance to IBM Software Hub Version 5.2.
Options What to do The cluster administrator will upgrade the instance An instance administrator will upgrade the instance, but the user has the adminrole on the projectsAn instance administrator will upgrade the instance, and the user has the minimum permissions to install the software - c. Do you need to update your entitlements?
- You are required to keep a record of the size of deployments to report to IBM as requested. The License Service measures your use against your license terms.
| Options | What to do |
|---|---|
| You are not changing the solutions or services associated with the instance | |
| You are changing one or more solutions or services associated with the instance |
|
8. Upgrading an instance of IBM Cloud Pak for Data
To upgrade an instance of IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2, you must update the operators and operands (custom resources) that are associated with the instance.
Instance administrator
Repeat as needed
- a. Upgrading to IBM Software Hub
-
To upgrade an instance of IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2, you must upgrade the required operators and custom resources for the instance. After you upgrade the required operators for the instance, you must upgrade the operators for the services that are installed on the instance.
What to do - b. Upgrading the
cpdbrservice -
You must upgrade the
cpdbrservice after you upgrade IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2.Options What to do You do not use the cpdbrservice to back up and restore your IBM Software Hub deploymentYou use the cpdbrservice to back up and restore your IBM Software Hub deployment
9. Installing or upgrading the privileged monitoring service
Privileged monitors provide additional information about the health of the cluster and resources that are not typically included in the platform monitors. If you installed the privileged monitors, a cluster administrator must upgrade the monitors as part of the upgrade from IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2.
Cluster administrator
Repeat as needed
Monitors provided by the privileged monitoring service
- Cluster operator status check (
check-cluster-operator-status) - Checks the status of the cluster operators that comprise the Red Hat
OpenShift Container Platform infrastructure to determine whether:
- All of the operators are
AVAILABLE - Any of the operators are
DEGRADED
- All of the operators are
- Network status check (
check-network-status) - Checks the status of the
PodNetworkConnectivityCheckobjects for cluster resources to determine whether the objects areReachable. - Node imbalance status check (
check-node-imbalance-status) - Checks whether vCPU requests are balanced across nodes or whether one node is supporting a disproportionately high load.
- Node status check (
check-node-status) - Checks whether the nodes on the cluster are ready and whether the nodes are using too many resources.
- Volume usage status check (
check-volume-status) - Checks whether the persistent volume claims associated with the deployment are running out of
space.Restriction: Only persistent volume claims that are mounted by a running pod are monitored.
- Operator namespace status check (
check-operator-namespace-status) - Checks whether the resources in the operators project for the deployment are
healthy.Important: If you also want to check the status of the operators in the project where the scheduling service is installed, you must run the
apply-privileged-monitoring-servicecommand with the--cluster_components_ns=${PROJECT_SCHEDULING_SERVICE}option. - EDB cluster status check (
check-edb-cluster-status) - Checks whether any instances of EDB Postgres that are associated with the deployment are healthy. For example, whether the database that IBM Software Hub uses to store metadata for the deployment is healthy.
| Options | What to do |
|---|---|
| You did not install the privileged monitoring service, and you don't plan to install it | |
| You did not install the privileged monitoring service, but you plan to install it | |
| You installed the privileged monitoring service |
10. Installing or upgrading the admission controller webhook
The configuration admission controller webhook enables services to use a shared set of custom certificates. If you installed the configuration admission controller webhook on IBM Cloud Pak for Data Version 5.0, a cluster administrator must upgrade the webhook after you upgrade the control plane from IBM Cloud Pak for Data Version 5.0 to IBM Software Hub Version 5.2.
Cluster administrator
Repeat as needed
Services that support shared custom certificates
- AI Factsheets
- Analytics Engine powered by Apache Spark
- Cognos Analytics
- Data Privacy
- DataStage
- Data Virtualization
- Db2 Big SQL
- IBM Match 360
- OpenPages
- RStudio®
- Watson Studio
- Watson Studio Runtimes
- watsonx Assistant
- watsonx.data
- watsonx Orchestrate
| Options | What to do |
|---|---|
| You did not install the admission controller webhook, and you don't plan to install it | |
| You did not install the admission controller webhook, but you plan to install it | |
| You installed the admission controller webhook |
11. Completing post-upgrade tasks
After you upgrade to IBM Software Hub, determine whether there are any additional tasks that you should complete to configure your installation.
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 |
|