Chapter 5. Migrating 3scale template to operator-based deployments
Prerequisites
- Red Hat 3scale API Management 2.7 deployed in both environments.
A domain for each OpenShift cluster, and another WILDCARD_DOMAIN for 3scale. Examples:
-
Red Hat OpenShift 3.11 (OCP3):
ocp3.example.com -
Red Hat OpenShift 4.x (OCP4):
ocp4.example.com -
3scale:
3scale.example.com
-
Red Hat OpenShift 3.11 (OCP3):
Procedure
The basic setup before migration is that 3scale points to the OCP3 domain: 3scale.example.com ocp3.example.com
To migrate 3scale from a template-based deployment using Red Hat OpenShift 3.11 to an operator-based deployment using Red Hat OpenShift 4.1, follow these steps:
- Create a 3scale backup from the template-based deployment.
- Deploy 3scale using the operator.
- Restore the backup in the operator-based deployment.
-
Point the 3scale WILDCARD_DOMAIN, in this case
3scale.example.com, toocp4.example.com.
After you have performed all the listed steps, 3scale migration from a template to an operator-based deployment is now complete.
