Upgrading Watson Discovery from Version 5.1 to Version 5.2

An instance administrator can upgrade Watson Discovery from Version 5.1 to Version 5.2.

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.2.2, you must upgrade Watson Discovery to Version 5.2.2.

Environment variables

The commands in this task use environment variables so that you can run the commands exactly as written.

If you don't 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:

System requirements

This task assumes that the cluster meets the minimum requirements for Watson Discovery.

Where to find more information
If this task is not complete, see System requirements.

Workstation

This task assumes that the workstation from which you will run the upgrade is set up as a client workstation and has the following command-line interfaces:

IBM Software Hub CLI: cpd-cli
OpenShift® CLI: oc

Where to find more information
If this task is not complete, see Updating client workstations.

Control plane

This task assumes that the IBM Software Hub control plane is upgraded.

Where to find more information
If this task is not complete, see Upgrading an instance of IBM Software Hub.

Private container registry

If your environment uses a private container registry (for example, your cluster is air-gapped), this task assumes that the following tasks are complete:

The Watson Discovery software images are mirrored to the private container registry.
Where to find more information

If this task is not complete, see Mirroring images to a private container registry.
The cpd-cli is configured to pull the olm-utils-v3 image from the private container registry.
Where to find more information

If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.

Multicloud Object Gateway

Where to find more information
If this task is not complete, see Mirroring images to a private container registry.

Where to find more information
If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.

This task assumes that Multicloud Object Gateway is upgraded, if needed.

Where to find more information
If this task is not complete, see Upgrading Multicloud Object Gateway.

Procedure

Complete the following tasks to upgrade Watson Discovery:

Specifying configuration options
Upgrading the service
Validating the upgrade
Upgrading existing service instances
Applying a hotfix for OpenSearch
What to do next

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

Property	Description
`discovery_deployment_type`	The deployment type for Watson Discovery. The deployment type determines the number of resources allocated to Watson Discovery. Default value `Production` Valid values `Production` A production deployment has at least two replicas of each pod to support production-scale workloads. For the production deployment, the deployment size is the small `scaleConfig` setting. `Starter` A starter deployment has fewer resources and less computing power than a production deployment. For the starter deployment, the deployment size is the xsmall `scaleConfig` setting. In previous releases, this deployment type was called the `development` deployment type.

discovery_deployment_type

The deployment type for Watson Discovery.

The deployment type determines the number of resources allocated to Watson Discovery.

Default value

Production

Valid values

Production: A production deployment has at least two replicas of each pod to support production-scale workloads. For the production deployment, the deployment size is the small scaleConfig setting.
Starter: A starter deployment has fewer resources and less computing power than a production deployment. For the starter deployment, the deployment size is the xsmall scaleConfig setting.
In previous releases, this deployment type was called the development deployment type.

Upgrading the service

Important: The Operator Lifecycle Manager (OLM) objects for Watson Discovery were updated when you upgraded the IBM Software Hub platform. The

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 the cpd-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

Watson Discovery is upgraded when the 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.

Applying a hotfix for OpenSearch

5.2.0

Note: This section is applicable only when you are upgrading to Version 5.2.0.

After upgrading to Version 5.2.0, you must apply this hotfix for OADP online restore to work with Watson Discovery. For more information, see Applying a hotfix for OpenSearch.

What to do next

Watson Discovery is ready to use. For information about how to give people access to your instance, see Administering Watson Discovery.