Upgrading Watson Discovery from Version 4.8 to Version 5.1
An instance administrator can upgrade Watson Discovery from IBM Cloud Pak® for Data Version 4.8 to IBM Software Hub Version 5.1.
- Who needs to complete this task?
-
Instance administrator To upgrade Watson Discovery, you must be an instance administrator. An instance administrator has permission to manage software in the following projects:
- The operators project for the instance
-
The operators for this instance of Watson Discovery are installed in the operators project. In the upgrade commands, the
${PROJECT_CPD_INST_OPERATORS}
environment variable refers to the operators project. - The operands project for the instance
-
The custom resources for the control plane and Watson Discovery are installed in the operands project. In the upgrade commands, the
${PROJECT_CPD_INST_OPERANDS}
environment variable refers to the operands project.
- When do you need to complete this task?
-
Review the following options to determine whether you need to complete this task:
- If you want to upgrade the IBM Software Hub control plane and one or more services at the same time, follow the process in Upgrading an instance of IBM Software Hub instead.
- If you didn't upgrade Watson
Discovery when you upgraded the IBM Software Hub
control plane, complete this task to upgrade Watson
Discovery.
Repeat as needed If you are responsible for multiple instances of IBM Software Hub, you can repeat this task to upgrade more instances of Watson Discovery on the cluster.
Information you need to complete this task
Review the following information before you upgrade Watson Discovery:
- Version requirements
-
All the components that are associated with an instance of IBM Software Hub must be installed at the same release. For example, if the IBM Software Hub control plane is at Version 5.1.1, you must upgrade Watson Discovery to Version 5.1.1.
- Environment variables
- The commands in this task use environment variables so that you can run the commands exactly as
written.
- If you do not have the script that defines the environment variables, see Setting up installation environment variables.
- To use the environment variables from the script, you must source the environment variables
before you run the commands in this task. For example,
run:
source ./cpd_vars.sh
Before you begin
This task assumes that the following prerequisites are met:
Prerequisite | Where to find more information |
---|---|
The cluster meets the minimum requirements for Watson Discovery. | If this task is not complete, see System requirements. |
The workstation from which you will run the upgrade is set up as a client workstation and
has the following command-line interfaces:
|
If this task is not complete, see Updating client workstations. |
The IBM Software Hub control plane is upgraded. | If this task is not complete, see Upgrading an instance of IBM Software Hub. |
For environments that use a private container registry, such as air-gapped environments, the Watson Discovery software images are mirrored to the private container registry. | If this task is not complete, see Mirroring images to a private container registry. |
For environments that use a private container registry, such as air-gapped environments,
the cpd-cli is configured to pull the olm-utils-v3 image from the private container registry. |
If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry. |
Multicloud Object Gateway is upgraded, if needed. | If this task is not complete, see Upgrading Multicloud Object Gateway. |
Procedure
Complete the following tasks to upgrade Watson Discovery:
Specifying installation options
When you upgrade Watson
Discovery, you can specify the following options in the install-options.yml
file in the work
directory.
################################################################################
# Watson Discovery parameters
################################################################################
#discovery_deployment_type: Production
Property | Description |
---|---|
discovery_deployment_type |
The deployment type for Watson Discovery. The deployment type determines the number of resources allocated to Watson Discovery.
|
Upgrading the service
cpd-cli
manage
apply-olm
updates all of the OLM objects in the operators project
at the same time.To upgrade Watson Discovery:
-
Log the
cpd-cli
in to the Red Hat® OpenShift Container Platform cluster:${CPDM_OC_LOGIN}
Remember:CPDM_OC_LOGIN
is an alias for thecpd-cli manage login-to-ocp
command. - Update the custom resource for Watson
Discovery.
cpd-cli manage apply-cr \ --components=watson_discovery \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true \ --upgrade=true
Validating the upgrade
apply-cr
command
returns:[SUCCESS]... The apply-cr command ran successfully
If you want to confirm that the custom resource status is
Completed
, you can run the cpd-cli
manage
get-cr-status
command:
cpd-cli manage get-cr-status \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watson_discovery
Upgrading existing service instances
The service instances are automatically upgraded when you upgrade Watson Discovery.
Removing the previous PostgreSQL cluster
Starting in IBM Software Hub Version 5.1, PostgreSQL is migrated to version 16. After you upgrade Watson Discovery, you must remove the previous PostgreSQL cluster.
- Confirm that the status of the Watson
Discovery service is shown as
READY
.oc get watsonDiscovery wd --namespace=${PROJECT_CPD_INST_OPERANDS}
- Run the following command to remove the previous PostgreSQL
cluster:
oc delete cluster.postgresql wd-discovery-cn-postgres