Updating the shared cluster components for a remote physical location (Upgrading from Version 5.2 to Version 5.4)

After you upgrade the IBM® Software Hub instance on your primary cluster (the hub), you must upgrade the shared cluster components 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.

When do you need to complete this task?

One-time setup Complete this task one time on each cluster where a remote physical location is running.

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

About this task

You must upgrade the shared cluster components on the remote cluster:
  • License Service
  • Scheduling service

The components are cluster-wide components, which means that they are installed once and shared by any remote physical locations on the cluster.

Procedure

  1. 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.
  2. Upgrade the License Service: 
    cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--license_acceptance=true \
--licensing_ns=${REMOTE_PROJECT_LICENSE_SERVICE}

    Wait for the cpd-cli to return the following message before proceeding to the next step:

    [SUCCESS] ... The apply-cluster-components command ran successfully.
  3. Upgrade the scheduling service: 
    cpd-cli manage apply-scheduler \
--release=${VERSION} \
--license_acceptance=true \
--scheduler_ns=${REMOTE_PROJECT_SCHEDULING_SERVICE} \
--remote_cluster=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 IBM Software Hub agents on a remote physical location (Upgrading from Version 5.2 to Version 5.4).