Upgrading from IBM Cloud Pak for Data Version 4.7 to Version 5.0
Services that cannot be upgraded to Version 5.0
- Watson Knowledge Studio
-
The Watson Knowledge Studio service was deprecated in Version 4.7 and is not available in Version 5.0.
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 5.0. For more information, see Uninstalling Watson Knowledge Studio in the Version 4.7 documentation.
Before you begin
- Review the information in the Planning section.
Specifically, ensure that you review the System requirements. Your cluster must have sufficient resources to upgrade to Cloud Pak for Data Version 5.0.
- 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 in the Version 4.7 documentation.
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
Restriction: Starting in IBM Cloud Pak for Data Version 5.0, Data Virtualization and Db2 Big SQL are not supported on Red Hat OpenShift Container Platform Version 4.12. If your environment includes either service, you must upgrade your cluster to Red Hat OpenShift Container Platform Version 4.14 or later after you upgrade to IBM Cloud Pak for Data Version 5.0.
Options What to do You are running a supported version of OpenShift You are running an older version of OpenShift - b. Are you running a supported version of your persistent storage?
-
Supported versions of persistent storage
Storage option Version supported in 5.0 Upgrade notes OpenShift Data Foundation - Version 4.12 or later fixes
- Version 4.14 or later fixes
- Version 4.15 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 Data Foundation 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 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 23.07 or later fixes No action is required.
Options What to do You are running a supported version of your persistent storage You have an older version of your persistent storage
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
What to do |
---|
3. Collecting required information
To successfully upgrade from IBM Cloud Pak for Data Version 4.7 to Version 5.0, you must have specific information about your environment.
Cloud Pak for Data operations team
Repeat as needed
What to do |
---|
|
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
What to do |
---|
|
5. Preparing to run upgrades from a private container registry
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.
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.
- 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 5.0 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 5.0).
- 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-v3
image from the private container registry? -
If the
olm-utils-v3
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. 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
Services with a dependency on prerequisite software
Services that have prerequisites | Prerequisite software |
---|---|
Watson Discovery | To install this service, you must install the following software:
|
Watson Speech services | To install this service, you must install the following software:
|
watsonx Assistant | To install this service, you must install the following software:
If you plan to use conversational skills or conversational search features, you must install the following operators:
|
Options | What to do |
---|---|
You do not have any services with a dependency on prerequisite software | |
You have services with a dependency on prerequisite software |
|
8. Preparing to upgrade an instance of Cloud Pak for Data
Before you upgrade an instance of IBM Cloud Pak for Data to Version 5.0, a cluster administrator must prepare the instance for upgrade.
Cluster administrator
Repeat as needed
- a. Who will upgrade the instance?
- 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.
Options What to do The cluster administrator will upgrade the instance Another user will upgrade the instance - Complete the appropriate task in Reauthorizing the instance administrator (Upgrading from Version 4.7 to Version 5.0).
- Go to b. Do you want to install the privileged monitoring service?
- b. Do you want to install 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.
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
PodNetworkConnectivityCheck
objects 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-service
command 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 Cloud Pak for Data uses to store metadata for the deployment is healthy.
Options What to do You do not want to install the privileged monitoring service You want to install the privileged monitoring service - Cluster operator status check (
- c. Do you need to install the configuration admission controller webhook?
-
If you want to enable services to use a shared set of custom certificates, a cluster administrator must install the Cloud Pak for Data configuration admission controller webhook.
Services that support shared custom certificates
- AI Factsheets
- Cognos Analytics
- Data Privacy
- DataStage
- Data Virtualization
- Db2 Big SQL
- OpenPages
Options What to do You do not need to install the configuration admission controller webhook You need to install the configuration admission controller webhook - d. Do you need to install or upgrade the resource specification injection webhook?
-
The resource specification injection (RSI) webhook is required if you plan to use node pinning to manage entitlement or if you want to apply your cluster-level HTTP proxy configuration to your IBM Cloud Pak for Data. If you installed the RSI webhook in Cloud Pak for Data Version 4.7, a cluster administrator must upgrade the webhook as part of the upgrade to Version 5.0
Options What to do You do not need to install or upgrade the RSI webhook You need to install or upgrade the RSI webhook - e. Do you need to apply or 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.
Situations that require you to run the apply-entitlement command
- You did not run the
cpd-cli manage apply-entitlement
command when you installed Cloud Pak for Data Version 4.7. - You plan to change the software that is deployed in an instance of Cloud Pak for Data when you upgrade to Cloud Pak for Data Version 5.0.
- You want to use node pinning to comply with your license terms.
Options What to do You do not need to apply or update your entitlements You need to apply or update your entitlements - Complete the appropriate task in Applying your entitlements to monitor and report use against license terms (Upgrading from Version 4.7 to Version 5.0).
- Go to 9. Upgrading an instance of Cloud Pak for Data.
- You did not run the
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 - 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
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
Options | What to do |
---|---|
You upgraded the services when you upgraded the platform |
Remember: If your environment includes
Data Virtualization or Db2
Big SQL, you must upgrade your cluster to Red Hat
OpenShift Container Platform Version 4.14 or later after you upgrade to
IBM Cloud Pak for Data Version 5.0.
|
You didn't upgrade the services when you upgraded the platform |
Remember: If your environment includes
Data Virtualization or Db2
Big SQL, you must upgrade your cluster to Red Hat
OpenShift Container Platform Version 4.14 or later after you upgrade to
IBM Cloud Pak for Data Version 5.0.
|