Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
Chapter 2. APIcast operator-based upgrade guide: from 2.12 to 2.13
Upgrading APIcast from 2.12 to 2.13 in an operator-based installation helps you use the APIcast API gateway to integrate your internal and external API services with 3scale.
To understand the required conditions and procedures, 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, be sure to have a maintenance window.
2.1. Prerequisites to perform the upgrade
To perform the upgrade of APIcast from 2.12 to 2.13 in an operator-based installation, the following required prerequisites must already be in place:
- An OpenShift Container Platform (OCP) 4.8, 4.9, 4.10, or 4.11 cluster with administrator access.
- APIcast 2.12 previously deployed via the APIcast operator.
Make sure the latest CSV of the
threescale-2.12channel is in use. To check it:- If the approval setting for the subscription is automatic you should already be in the latest CSV version of the channel.
- If the approval setting for the subscription is manual make sure you approve all pending InstallPlans and have the latest CSV version.
- Keep in mind if there is a pending install plan, there might be more pending install plans, which will only be shown after the existing pending plan has been installed.
2.2. Upgrading APIcast from 2.12 to 2.13 in an operator-based installation
Upgrade APIcast from 2.12 to 2.13 in an operator-based installation so that APIcast can function as the API gateway in your 3scale installation.
Procedure
- Log in to the OCP console using the account with administrator privileges.
- Select the project where the APIcast operator has been deployed.
- Click Operators > Installed Operators.
- In Subscription > Channel, select Red Hat Integration - 3scale APIcast gateway.
Edit the channel of the subscription by selecting the threescale-2.13 channel and save the changes.
This will start the upgrade process.
Query the pods status on the project until you see all the new versions are running and ready without errors:
oc get pods -n <apicast_namespace>
$ oc get pods -n <apicast_namespace>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note- The pods might have temporary errors during the upgrade process.
- The time required to upgrade pods can vary from 5-10 minutes.
Check the status of the APIcast objects and get the YAML content by running the following command:
oc get apicast <myapicast> -n <apicast_namespace> -o yaml
$ oc get apicast <myapicast> -n <apicast_namespace> -o yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
After you have performed all the listed steps, APIcast upgrade from 2.12 to 2.13 in an operator-based deployment is now complete.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}