Installing the shared cluster components for a remote physical location

Before you can install the IBM Software Hub agents on a remote cluster, you must prepare your remote Red Hat® OpenShift® Container Platform cluster.

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 you plan to create one or more remote physical locations.

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

To prepare a cluster to host a remote physical location, you must install the following software on the cluster:

  • IBM Certificate manager
  • 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. Install the IBM Certificate manager and License Service: 
    cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--license_acceptance=true \
--cert_manager_ns=${REMOTE_PROJECT_CERT_MANAGER} \
--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. Install 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 installed the shared cluster components for the remote physical location, you're ready to complete Creating the projects for a remote physical location.