Upgrading foundational services in an air-gapped environment

You can upgrade foundational services that were installed in a prior release in an airgap environment.

Supported upgrade paths

Note: For more information on migrating from foundational services version 3.x.x to version 4.x.x, see Migrating foundational services version 3.x to 4.x

You can upgrade only the following supported paths:

Table 1. Upgrade paths
Upgrade from	Upgrade to	Description	Steps
Version 4.x or later	A newer continuous delivery version (4.x or later)	Create new CatalogSource, and update channel and CatalogSource for operator's subscription	Upgrading from version 4.x or later to the newer continuous delivery version (4.x or later)

During the upgrade process, you cannot access the services management console.

Upgrading to the latest continuous delivery version

Upgrading from version 4.x or later to the latest continuous delivery version (4.x or later)

Upgrading foundational services Cert-Manager and Licensing Service

Log in to the cluster as an administrator by using the oc login command.
Mirror the images.
Create the catalog source.
Download the cp3pt0-deployment folder, from the installer_scripts folder in the CASE bundle. For information on downloading the scripts, see Downloading scripts for additional configuration from specific version CASE bundle.

Go to your downloaded installer_scripts directory.
```
cd ${installer_scripts}/cp3pt0-deployment
```
Read the script usage instructions by passing the -h flag to the script.
```
 ./setup_singleton.sh -h
```
Note: You can specify the following subscription channels for upgrade: v4.2 (the default channel is v4.2), v4.1, or v4.0.
- For upgrading to version 4.0.x, specify v4.0
- For upgrading to version 4.1.x, specify v4.1
- For upgrading to version 4.2.x, specify v4.2
Run the script by passing the parameters.

Note: You must provide the --license-accept parameters.
```
 ./setup_singleton.sh --license-accept \
   --enable-licensing \
   -c v4.3 \
```

Upgrading foundational services services

Log in to the cluster as an administrator by using the oc login command.
Mirror the images.
Create the catalog source.
Download the cp3pt0-deployment folder, from the installer_scripts folder in the CASE bundle. For information on downloading the scripts, see Downloading scripts for additional configuration from specific version CASE bundle.

Go to your downloaded installer_scripts directory.
```
cd ${installer_scripts}/cp3pt0-deployment
```
Read the script usage instructions by passing the -h flag to the script.
```
 ./setup_tenant.sh -h
```
Note: You can specify the following subscription channels for upgrade: v4.2 (the default channel is v4.2), v4.1, or v4.0.
- For upgrading to version 4.0.x, specify v4.0
- For upgrading to version 4.1.x, specify v4.1
- For upgrading to version 4.2.x, specify v4.2

Run the script by passing the parameters.

Note: You must provide the --license-accept and --operator-namespace parameters.

 ./setup_tenant.sh --license-accept \
   --enable-licensing \
   --operator-namespace <foundational-services-namespace> \
   -c v4.3 \
   -i Automatic \
   -s opencloud-operators \
   -n openshift-marketplace \
   -v 1

Upgrade steps

Mirror the images

You must download following CASE files to mirror, and import the images in your private container registry. Then complete the following steps in Installing your IBM Cloud Pak by mirroring Cloud Pak images to a private container registry (with ibm-pak plug-in).

ibm-cert-manager-4.1.0.tgz
ibm-licensing-4.1.0.tgz
ibm-cp-common-services-4.1.0.tgz

For more information, see IBM Catalog Management Plug-in for IBM Cloud Paks.

Create the catalog source

After you mirror the images, complete these steps:

Create the catalog source for the new version of foundational services to which you are upgrading.
```
 oc apply -f ~/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
```

Troubleshooting

If you encounter any issues during your upgrade, review the frequently encountered errors to help you troubleshoot your issue. For more information, see Troubleshooting IBM Cloud Pak foundational services install and upgrade.