Upgrading API Connect
Upgrade API Connect on Kubernetes and OpenShift platforms to a newer version.
Upgrading your API Connect deployment consists of three phases:
- Upgrade planning. Decide on your upgrade path based on your platform and current version. It
might be necessary to upgrade your container environment before you can upgrade API Connect.
Review any feature changes in the new API Connect version that might impact how you use API Connect and plan for such changes.
Upgrade planning should be started as early as possible to identify any issues that might influence when you are able to upgrade, and any actions to take before upgrade.
- Upgrade preparation. Run pre-upgrade checks on your current deployment, download the new version
of API Connect from Fix Central, backup your current deployment. Upgrade your container platform if
required.
Upgrade preparation can be done at any time, and it is worth doing early to identify and fix any potential problems before your upgrade window. If you do complete the upgrade preparation early, repeat the pre-upgrade checks just before your upgrade window to check for any new problems.
- Upgrade procedure. Updating your API Connect
operator and operands to the new version. Upgrading cert-manager might also be
necessary.
The upgrade process should be started only when all upgrade planning and preparation are completed. Interrupting and rolling back API Connect upgrades is not possible. Disaster recovery procedures must be followed to restore API Connect to the old version if problems are encountered during upgrade.