You can upgrade common services that were installed in a prior release.
Important: You must first upgrade common services from version 3.4.x to version 3.5.x. Then, upgrade the IBM Cloud Pak® for Multicloud Management. After you upgrade the IBM Cloud Pak for Multicloud Management, you can optionally upgrade common services to version 3.6.x.
You can upgrade only the following supported paths:
Common services installer version 3.4.x to common services installer version 3.5.x.
quay.io/opencloudio/ibm-common-service-catalog:3.5.6.Common services installer version 3.5.x to common services installer version 3.6.x.
quay.io/opencloudio/ibm-common-service-catalog:3.5.6 to quay.io/opencloudio/ibm-common-service-catalog:3.6.2 Or, you can change the tag to latest to automatically complete future upgrades to the most current version.You can edit the IBM Cloud Platform Common 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.
Verify the upgrade by completing these steps:
Check whether the cp-console and cp-proxy routes exist in the ibm-common-services namespace by running the following command:
oc get route -n ibm-common-services
If the cp-proxy route is missing, you might see an "Application not available" error and be unable to access a IBM Cloud Pak® application. To add the missing route, delete the cp-console route. This action
causes the ibm-management-ingress-operator to re-create both routes. To delete the cp-console route, run the following command:
oc delete route cp-console -n ibm-common-services
After the routes are re-created, you can access your IBM Cloud Pak® application.
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 Platform Common Services install and upgrade.