Pulling the `olm-utils-v2` image from the private container registry (Upgrading from Version 4.5 to Version 4.7)

Important: IBM Cloud Pak® for Data Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

If the olm-utils-v2 image is available in the private container registry, you must update the cpd-cli to pull the image from the private container registry.

Upgrade phase: Updating your client workstation; Updating your cluster; Collecting required information; Preparing to run an upgrade from a private container registry; Migrating to the private topology; Preparing to upgrade an instance of Cloud Pak for Data; Upgrading an instance of Cloud Pak for Data
Who needs to complete this task?: All administrators Any user who is involved in upgrading Cloud Pak for Data must complete this task on their workstation.
When do you need to complete this task?: One-time setup If you pull images from a private container registry, complete this task before you run the cpd-cli manage commands against a cluster in a restricted network.

Before you begin

A private container registry administrator must complete Mirroring images to a private container registry (Upgrading from Version 4.5 to Version 4.7).
You must have the cpd-cli installed on the workstation where you complete this task. For details, see Installing the IBM Cloud Pak for Data command-line interface.

Procedure

Determine whether you have the OLM_UTILS_IMAGE environment variable in your environment variable script.

If you already have the OLM_UTILS_IMAGE environment variable in your script, update the command to point to the olm-utils-v2 image.

x86-64 clusters

export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/olm-utils-v2:${VERSION}

ppc64le clusters

export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/olm-utils-v2:${VERSION}.ppc64le

s390x clusters

export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/olm-utils-v2:${VERSION}.s390x

If you don't have the OLM_UTILS_IMAGE environment variable in your script, update the script on your workstation to include the OLM_UTILS_IMAGE environment variable:

x86-64 clusters

export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/olm-utils-v2:${VERSION}

ppc64le clusters

export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/olm-utils-v2:${VERSION}.ppc64le

s390x clusters

export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/olm-utils-v2:${VERSION}.s390x

Results

When you run the

cpd-cli
manage

commands, the workstation will automatically pull the olm-utils-v2 image from the private container registry.

What to do next

Now that you've configured the cpd-cli to pull the olm-utils-v2 image from the private container registry, you're ready to complete Migrating to the private topology (Upgrading from Version 4.5 to Version 4.7).