Upgrading foundational services

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

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 from version 4.x or later to the latest continuous delivery version (4.x or later)

Upgrading foundational services Cert-Manager and Licensing Service

Update the ibm-licensing-catalog catalogsource for the most recent release version.

 apiVersion: operators.coreos.com/v1alpha1
 kind: CatalogSource
 metadata:
   name: ibm-licensing-catalog
   namespace: openshift-marketplace
 spec:
   displayName: ibm-licensing-4.1.0
   publisher: IBM
   sourceType: grpc
   image: icr.io/cpopen/ibm-licensing-catalog
   updateStrategy:
     registryPoll:
       interval: 45m

Update the ibm-cert-manager-catalog catalogsource for the most recent release version.

 apiVersion: operators.coreos.com/v1alpha1
 kind: CatalogSource
 metadata:
   name: ibm-cert-manager-catalog
   namespace: openshift-marketplace
 spec:
   displayName: ibm-cert-manager-4.1.0
   publisher: IBM
   sourceType: grpc
   image: icr.io/cpopen/ibm-cert-manager-operator-catalog
   updateStrategy:
     registryPoll:
       interval: 45m

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.1 (the default channel version is 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
Run the script by passing the parameters.

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

Upgrading foundational services services

Update the opencloud-operator catalogsource to latest for the most recent release version.

 apiVersion: operators.coreos.com/v1alpha1
 kind: CatalogSource
 metadata:
   name: opencloud-operators
   namespace: openshift-marketplace
 spec:
   displayName: IBMCS Operators
   publisher: IBM
   sourceType: grpc
   image: icr.io/cpopen/ibm-common-service-catalog:latest
   updateStrategy:
     registryPoll:
       interval: 45m

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.1 (the default channel version is 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

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.1 \
   -i Automatic \
   -s opencloud-operators \
   -n openshift-marketplace \
   -v 1

Approval strategy for future upgrades

You can decide on the approval strategy for future upgrades by setting the InstallPlanApproval parameter in the custom resource to either Automatic or Manual, as required. For more information, see Configuring IBM Cloud Pak foundational services by using the CommonService custom resource.

Troubleshooting

If you encounter any issue 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 and Troubleshooting IBM Cloud Pak foundational services upgrade.