Updating the IBM Software Hub agents on a remote physical location (Upgrading from Version 5.0 to Version 5.1)

After you upgrade the IBM Software Hub instance on your primary cluster (the hub), you must upgrade IBM Software Hub agents on the remote physical locations that connect to the hub.

Who needs to complete this task?: Cluster administrator A cluster administrator must complete this task.

Important: In addition, you must have the Manage physical locations (manage_locations) permission on the instance of IBM Software Hub that the remote physical location connects to.

When do you need to complete this task?: Repeat as needed Complete this task for each remote physical location that connects to the hub.

Before you begin

Best practice: You can run the commands in this task exactly as written if you use set up environment variables for the remote physical location in addition to the installation environment variables script. For instructions, see Setting up environment variables for a remote physical location.

Before you run the commands in this task, ensure that you source the environment variables for:

The primary cluster
The remote physical location

Procedure

Log the cpd-cli in to the Red Hat® OpenShift® Container Platform cluster:
```
${REMOTE_CPDM_OC_LOGIN}
```
Remember: REMOTE_CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command when you are connecting to a remote cluster.

Upgrade the IBM Software Hub agents on the remote physical location.

The command that you run depends on whether you want to pull the images from the IBM Entitled Registry or from a private container registry:

The remote cluster pulls images from the IBM Entitled Registry

cpd-cli manage create-physical-location \
--physical_location_name=${REMOTE_PHYSICAL_LOCATION_ID} \
--management_ns=${REMOTE_PROJECT_MANAGEMENT} \
--cpd_hub_url=${CPD_HUB_URL} \
--cpd_hub_api_key=${CPD_HUB_API_KEY} \
--release=${VERSION} \
--upgrade=true

The remote cluster pulls images from a private container registry

cpd-cli manage create-physical-location \
--physical_location_name=${REMOTE_PHYSICAL_LOCATION_ID} \
--management_ns=${REMOTE_PROJECT_MANAGEMENT} \
--cpd_hub_url=${CPD_HUB_URL} \
--cpd_hub_api_key=${CPD_HUB_API_KEY} \
--release=${VERSION} \
--image_prefix=${PRIVATE_REGISTRY_LOCATION} \
--upgrade=true

What to do next

Now that you've upgraded the shared cluster components for the remote physical location, you're ready to complete Updating the service-specific software on a remote physical location (Upgrading from Version 5.0 to Version 5.1).