Upgrading from version 3.4.x and 3.5.x to version 3.6.x
Before you upgrade the foundational services installer version, make sure that the installer catalog source image has the correct tag.
If, during installation, you had set the catalog source image tag as latest, you do not need to manually change the tag.
If, during installation, you had set the catalog source image tag to a specific version, 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.
To update the tag, complete the following actions.
To update the catalog source image tag, run the following command.
oc edit catalogsource opencloud-operators -n openshift-marketplace
Update the image tag.
Change image tag to the specific version of 3.6.x. The 3.6.3 tag is used as an example here:
spec:
displayName: IBMCS Operators
image: 'docker.io/ibmcom/ibm-common-service-catalog:3.6.3'
publisher: IBM
sourceType: grpc
updateStrategy:
registryPoll:
interval: 45m
Change the image tag to latest to automatically upgrade to the most current version.
spec:
displayName: IBMCS Operators
image: 'icr.io/cpopen/ibm-common-service-catalog:latest'
publisher: IBM
sourceType: grpc
updateStrategy:
registryPoll:
interval: 45m
To check whether the image tag is successfully updated, run the following command:
oc get catalogsource opencloud-operators -n openshift-marketplace -o jsonpath='{.spec.image}{"\n"}{.status.connectionState.lastObservedState}'
The following sample output has the image tag and its status:
icr.io/cpopen/ibm-common-service-catalog:latest
READY%
https://www.ibm.com/docs/en/cpfs?topic=online-upgrading-foundational-services-from-operator-release
