Upgrading 3Scale patch releases with operator

[nilic]

We're currently on OCP v4.5 and operator-installed 3Scale APIManager v2.9 and looking into upgrading to OCP v4.6. 3scale API Management 2.9 Supported Configurations states that OCP v4.6 is supported since 3Scale v2.9.1.

How to perform 3Scale v2.9 -> v2.9.1 upgrade using the operator?

The operator was originally installed on version 0.6.0, but has since upgraded to 0.6.1 since Approval is set to Automatic:

The annotations on the APIManager instance still return the following :

apps.3scale.net/apimanager-threescale-version: "2.9"
apps.3scale.net/threescale-operator-version: 0.6.0

and 3Scale admin portal also displays 2.9 as the current version:

3Scale upgrade docs refer to a section called "Setting up the 3scale operator for micro releases" which I'm unable to find in the documentation.

[miguelsorianod]

Hi @nilic,

Thanks for opening the issue.

The information you show me seems correct:

• The CSV has been updated to v0.6.1 which is the CSV used for 3scale 2.9.1.
• Between 3scale 2.9.0 and 2.9.1 there was no change of operator code so the operator version did not change, and that's why you see 0.6.0 as the annotation. The operator code version (0.6.0) is a different and independent concept than the CSV version (0.6.1)
• About the version shown in the UI, I think it does not show bugfix level number version information. There are current plans to improve this in a future 3scale version.

Regarding the link to the "Setting up the 3scale operator for micro releases" document, it seems the link is not working. I will report this to the documentation team.

[nilic]

Hi @miguelsorianod ,

thanks for the quick reply.

Just to make sure I understood it right - does this mean that we currently are running 3Scale v2.9.1 and can proceed with the OCP v4.6 upgrade?

[miguelsorianod]

Hi @nilic,

If the CSV has been correctly upgraded to v0.6.1, all pods are running and the installation is working I'd say so. You can also check that the images that are specified in the CSV are being used (if you inspect the csv yaml you will see there are some URLs there for the different component images) in the component pods to be even more sure.

[nilic]

If you are referring to these images (passed as env vars to the operator pod):

it seems that they match the images currently being used by the running pods.

[miguelsorianod]

Then it seems it looks good :+1:

[dzabel]

We came across the same question before the update to Openshift 4.12. It would be desirable and more user friendly if the minor version could be determined not only by the image SHA values.

[briangallagher]

Will be implemented in this JIRA