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

If you need to run cpd-cli manage commands against a cluster in a restricted network and the olm-utils image is available in the private container registry, you must update the cpd-cli installation on your workstation to enable the workstation to pull the image from the private container registry.

Upgrade phase
You are not here. Setting up a client workstation
You are not here. Collecting required information
You are here icon. Preparing your cluster
You are not here. Upgrading the Cloud Pak for Data platform and services
Who needs to complete this task?
Users who plan to complete the upgrade in a restricted network must complete this task on their workstation if they did not complete Updating the olm-utils image on a single client workstation (Upgrading from Version 4.5 to Version 4.6).
When do you need to complete this task?
Complete this task before you run the cpd-cli manage commands against a cluster in a restricted network.

Before you begin

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, no additional steps are required.
  • 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}/cpd/olm-utils:latest
    s390x clusters
    export OLM_UTILS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/cpd/olm-utils:latest.s390x
    Remember: You must source the environment variables each time you open a new bash prompt. For example:
    source ./cpd_vars.sh

Results

When you run the cpd-cli manage commands, the workstation will automatically pull the olm-utils image from the private container registry.