Upgrading IBM Cloud Pak foundational services online

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

Upgrading IBM Cloud Pak foundational services to version 3.6

IBM Cloud Pak foundational services installer version 3.5.x to IBM Cloud Pak foundational services installer version 3.6.x.
- If you installed IBM Cloud Pak foundational services version 3.5.x on an OpenShift Container Platform version 4.4 or version 4.5 cluster, and had set the catalog source image tag as latest, the IBM Cloud Pak foundational services are automatically upgraded to installer version 3.6.x. There is no manual step required for the upgrade.
- If you had set the installer catalog source image tag to a specific version during installation, you must update the tag with the version that you want to upgrade to. Or, you can change the tag to latest to automatically complete future upgrades to the most current version.

You can edit the IBM Cloud Pak foundational services catalog source tag by using the following command:

  oc -n openshift-marketplace edit catalogsource opencloud-operators

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

Edit the CatalogSource for IBM Cloud Pak foundational services by running the following command:
```
oc -n openshift-marketplace edit catalogsource opencloud-operators
```
In the result screen, modify the value of the image field to the following value:
```
 image: quay.io/opencloudio/ibm-common-service-catalog:3.12
```
Check whether quay.io/opencloudio/* is in the clusterimagepolicy repository by running the following command:
```
oc get clusterimagepolicy ibmcloud-default-cluster-image-policy -o yaml -n management-security-services
```
Note: The clusterimagepolicy exists only after you enabled securityServices and ibm-management-image-security-enforcement in the previous installation or upgrading process.

If not, you need to add quay.io/opencloudio/* to the clusterimagepolicy repository.
Edit the Subscription for IBM Cloud Pak foundational services by running the following command:
```
oc edit -n openshift-operators sub ibm-common-service-operator
```
In the result screen, modify the value of the channel field to the following value:
```
channel: v3
```
Wait for about ten minutes to allow the IBM Cloud Pak foundational services operators to complete the upgrading process. Check whether all IBM Cloud Pak foundational services pods are in running status by running the following command:
```
oc get pods -n ibm-common-services
```

Edit the CatalogSource for IBM Cloud Pak foundational services by running the following command:
```
oc -n openshift-marketplace edit catalogsource opencloud-operators
```
In the result screen, modify the value of the image field to the following value:
```
 image: quay.io/opencloudio/ibm-common-service-catalog:3.14
```
Check whether quay.io/opencloudio/* is in the clusterimagepolicy repository by running the following command:
```
oc get clusterimagepolicy ibmcloud-default-cluster-image-policy -o yaml -n management-security-services
```
Note: The clusterimagepolicy exists only after you enabled securityServices and ibm-management-image-security-enforcement in the previous installation or upgrading process.

If not, you need to add quay.io/opencloudio/* to the clusterimagepolicy repository.
Edit the Subscription for IBM Cloud Pak foundational services by running the following command:
```
oc edit -n openshift-operators sub ibm-common-service-operator
```
In the result screen, modify the value of the channel field to the following value:
```
channel: v3
```
Wait for about ten minutes to allow the IBM Cloud Pak foundational services operators to complete the upgrading process. Check whether all IBM Cloud Pak foundational services pods are in running status by running the following command:
```
oc get pods -n ibm-common-services
```

Edit the CatalogSource for IBM Cloud Pak foundational services by running the following command:
```
oc -n openshift-marketplace edit catalogsource opencloud-operators
```
In the result screen, modify the value of the image field to the following value:
```
 image: quay.io/opencloudio/ibm-common-service-catalog:3.18
```
Check whether quay.io/opencloudio/* is in the clusterimagepolicy repository by running the following command:
```
oc get clusterimagepolicy ibmcloud-default-cluster-image-policy -o yaml -n management-security-services
```
Note: The clusterimagepolicy exists only after you enabled securityServices and ibm-management-image-security-enforcement in the previous installation or upgrading process.

If not, you need to add quay.io/opencloudio/* to the clusterimagepolicy repository.
Edit the Subscription for IBM Cloud Pak foundational services by running the following command:
```
oc edit -n openshift-operators sub ibm-common-service-operator
```
In the result screen, modify the value of the channel field to the following value:
```
channel: v3
```
Wait for about ten minutes to allow the IBM Cloud Pak foundational services operators to complete the upgrading process. Check whether all IBM Cloud Pak foundational services pods are in running status by running the following command:
```
oc get pods -n ibm-common-services
```

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.