Chapter 1. 3scale migration guide: from template to operator-based deployments

This section contains information about migrating Red Hat 3scale API Management from a template-based deployment using Red Hat OpenShift 3.11, to an operator-based deployment using Red Hat OpenShift 4.x.

Warning

In order to understand the required conditions and procedure, read the entire migration guide before applying the listed steps. The migration process disrupts the provision of the service until the procedure finishes. Due to this disruption, make sure to have a maintenance window.

1.1. Prerequisites to perform the migration

Before migrating your 3scale installation from a template to an operator-based deployment, confirm that your deployment is supported by consulting the following guides:

1.2. Migrating 3scale template to operator-based deployments

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:

  1. Create a 3scale backup from the template-based deployment.
  2. Deploy 3scale using the operator.
  3. Restore the backup in the operator-based deployment.
  4. Point the 3scale WILDCARD_DOMAIN, in this case 3scale.example.com, to ocp4.example.com.

After you have performed all the listed steps, 3scale migration from a template to an operator-based deployment is now complete.