Upgrading the IBM Cloud Pak® in an airgap environment

Upgrade your IBM Cloud Pak® for Multicloud Management that was installed in a prior release in an airgap environment.

Notes:

• For IBM Cloud Pak® for Multicloud Management 2.3 and 2.3 Fix Pack 1, IBM Cloud Pak foundational services 3.6 and 3.12 are supported.
• For IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack 2, 3 and 4, IBM Cloud Pak foundational services 3.12 and 3.14 are supported.
• For IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack 5, IBM Cloud Pak foundational services 3.14, 3.18 and 3.19 are supported.
• For IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack 6, IBM Cloud Pak foundational services 3.19.6 is supported.
• For IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack 7, IBM Cloud Pak foundational services 3.19.13 and later versions are supported.

Prerequisites

• Install IBM Cloud Pak® CLI Version 3.4.4 or higher, and skopeo CLI version 1.1.1 or higher in your IBM Cloud Pak for Multicloud Management cluster or on a system that you use to acees the cluster. For more information about installing the IBM Cloud Pak® CLI, see Install the IBM Cloud Pak® CLI.

• Your cluster nodes must be healthy and in a Ready state. For more information. see Check cluster health.

Upgrade procedure

These instructions are for IBM Cloud Pak for Multicloud Management that was installed in an airgap environment. Your environment might already have a prepared bastion host, and the required Docker registries.

You need to download the case archive file base on the version that you want to upgrade to, and mirror and import the images in your airgap environment image registry. See the following case archive names:

2.3 Fix Pack 7: ibm-cp-management-100.3.32+2.3.29.tgz
2.3 Fix Pack 6: ibm-cp-management-100.3.30+2.3.28.tgz
2.3 Fix Pack 5: ibm-cp-management-100.3.28+2.3.27.tgz
2.3 Fix Pack 4: ibm-cp-management-100.3.25+2.3.24.tgz
2.3 Fix Pack 3: ibm-cp-management-100.3.24+2.3.23.tgz
2.3 Fix Pack 2: ibm-cp-management-100.3.22+2.3.21.tgz
2.3 Fix Pack 1: ibm-cp-management-100.3.10+2.3.10.tgz
2.3: ibm-cp-management-100.3.0+2.3.2.tgz

1. Complete the following sections from the Preparing an offline cluster for installation topic that is applicable to the type of host or device that you are using:

   • If you are using a bastion host, complete these steps from the Preparing for installation by using a bastion host topic:
     1. Create environment variables for the installer and image inventory
     2. Download the IBM Cloud Pak® installer and image inventory
     3. Log in to the OpenShift Container Platform as a cluster administrator
     4. Obtain the entitlement key to mirror the images
   • If you are using a portable compute device, complete these steps from the Preparing for installation by using a portable compute device topic:
     1. Create environment variables for the installer and image inventory
     2. Download the IBM Cloud Pak for Multicloud Management installer and image inventory
     3. Create the portable Docker registry
     4. Mirror the images to the portable Docker registry
        1. Obtain the entitlement key
        2. Mirror the images
     5. Connect the portable host to the airgap network
        1. Log in to the OpenShift Container Platform cluster as a cluster administrator
   • If you are using a portable storage device, complete these steps from the Preparing for installation by using a portable storage device topic:
     1. Create environment variables for the installer and image inventory
     2. Download the IBM Cloud Pak for Multicloud Management installer and image inventory
     3. Create the external Docker registry
     4. Mirror the images to the external Docker registry
        1. Obtain the entitlement key
        2. Mirror the images
     5. (Optional) Save the Docker registry image
     6. Copy the saved offline data to a portable storage device
     7. Prepare the host that has access to the OpenShift Container Platform cluster
        1. Log in to the OpenShift Container Platform as a cluster administrator
        2. Create a Kubernetes namespace for IBM Cloud Pak for Multicloud Management

2. Run the following command to avoid certificate validation issues:

   export GODEBUG=x509ignoreCN=0
   

3. Mirror the images by completing the following step from the preparation topic:

   • If you are using a bastion host, Mirror the images and configure the cluster.
   • If you are using a portable compute device, Configure the cluster and mirror the images.
   • If you are using a portable storage device, Prepare the internal host and extract images.

4. After you mirror the images, complete these steps to create the new IBM Cloud Pak® for Multicloud Management catalog source:

   1. Log in to your OpenShift Container Platform console.

   2. Remove the catalog sources that you created in Version 2.2.x.

      oc delete catalogsource ibm-management-orchestrator -n openshift-marketplace
      

   3. Create the Version 2.3.1 catalog source.

      cloudctl case launch \
        --case $OFFLINE_DIR/${CASE_ARCHIVE} \
        --inventory ${CASE_INVENTORY_SETUP} \
        --action install-catalog \
        --namespace ${NAMESPACE} \
        --args "--registry ${LOCAL_DOCKER_REGISTRY} --inputDir $OFFLINE_DIR" \
        --tolerance 1
      

      Note: The variable $OFFLINE_DIR is set in Preparing for installation by using a bastion host, and is the directory that serves as the offline store to store this current release installer and image inventory.

   4. Update the subscription channel of the ibm-management-orchestrator operator.

      oc patch sub ibm-management-orchestrator -p '{"spec":{"channel":"2.3-stable","source": "ibm-management-orchestrator"}}' --type=merge -n openshift-operators
      

   After the catalog source is created, the IBM Cloud Pak for Multicloud Management installer operator updates the installed services and modules operators to their latest version.

5. Complete the post upgrade tasks. For more information, see Post-upgrade tasks.