Chapter 2. 3scale operator-based upgrade guide: from 2.7 to 2.8
This section contains information about upgrading Red Hat 3scale API Management from version 2.7 to 2.8, in an operator-based deployment.
In order to understand the required conditions and procedure, read the entire upgrade guide before applying the listed steps. The upgrade process disrupts the provision of the service until the procedure finishes. Due to this disruption, make sure to have a maintenance window.
Prerequisites
- 3scale 2.7 previously deployed via the 3scale operator.
- An OpenShift Container Platform (OCP) 4.x cluster with administrator access.
2.1. Upgrading 3scale 2.7 to 2.8
To upgrade 3scale from version 2.7 to 2.8 in an operator-based deployment, use the following procedure.
Procedure
- Log in to the OCP console using the account with administrator privileges.
- Select the project where the 3scale-operator has been deployed.
- Click Operators > Installed Operators.
- Select 3scale operator Subscription > Channel.
Edit the channel of the subscription by selecting the threescale-2.8 and save the changes.
- This will start the upgrade process.
- Wait until the upgrade process finishes for the APIManager.
Query the pods status on the project:
oc get pods
- Wait until all the new versions are running and ready without errors.
They might have temporary errors during the upgrade process.
NoteTimes can vary from 5-10 minutes approximately. Be sure to keep checking the state of the pods until all of them are running, ready, and without errors.
- Confirm the upgrade process has been successful, by logging in to the 3scale Admin Portal and check that it works as expected.
Check the status of the APIManager objects and get the YAML content by running the following command:
oc get apimanager <myapimanager> -o yaml
The new annotations with the values should be shown as follows:
apps.3scale.net/apimanager-threescale-version: "2.8" apps.3scale.net/threescale-operator-version: "0.5.0"
After you have performed all the listed steps, 3scale upgrade from 2.7 to 2.8 in an operator-based deployment is now complete.