Prepare to Migrate Oracle Application Container Cloud Service to Oracle Cloud Infrastructure Container Engine for Kubernetes

2 Prepare to Migrate Oracle Application Container Cloud Service to Oracle Cloud Infrastructure Container Engine for Kubernetes

Plan the migration of your Oracle Application Container Cloud Service application to Oracle Cloud Infrastructure Container Engine for Kubernetes.

Topics:

Before You Begin

Before you start migrating your Oracle Application Container Cloud Service application, you need to meet certain prerequisites described in this section.

Ensure you have the following resources:

An Oracle Cloud Infrastructure tenancy and a user account
Access to an existing compartment. See Managing Compartments
User permissions to perform operations on the Oracle Cloud Infrastructure Container Engine for Kubernetes clusters and the Oracle Cloud Infrastructure Registry repositories. See Policy Configuration for Cluster Creation and Deployment and Policies to Control Repository Access
Generate an authentication token. See Getting an Auth Token
The application archive, including the manifest.json, and deployment.json files on your local disk. If you use the migration script tool, you may upload the application archive including the manifest.json and the deployment.json file in Oracle Cloud Infrastructure Object Storage and generate a pre-authenticated request for the object. See Managing Objects
(Optional) A public domain name (myapp.example.com) to use for the migrated application
(Optional) If your application requires an SSL endpoint, you need to obtain an SSL certificate and private key for your application

Additionally, ensure you have installed and configured the following software:

Docker Engine 17.03 or later (add the user to the Docker group. See Manage Docker as a non-root user)
Kubectl 1.7.4 or later
cURL or Wget
Python 2.7.5, 3.5, or later (Python is required if you're using the migration script tool.)
Oracle Cloud Infrastructure CLI 2.4 or later

Understand Downtime Requirements

The migration process in this guide does not impact the availability of your existing Oracle Application Container Cloud Service instance on Oracle Cloud Infrastructure Classic. This instance continues to run and can serve client requests during this process.

The process does not modify your deployed applications or significantly impact its performance.

After your applications are migrated successfully, clients can be rerouted to your applications running in Oracle Cloud Infrastructure.

Select Oracle Cloud Infrastructure Shapes

Identify compute shapes that provide similar IaaS resources in Oracle Cloud Infrastructure to the shapes that you're currently using for your service instances on Oracle Cloud Infrastructure Classic.

A compute shape defines the IaaS resources, such as OCPUs and memory, that are available to a specific node in a service instance. Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic each has its own set of standard compute shapes. See:

About Shapes in Using Oracle Cloud Infrastructure Compute Classic
Compute Shapes in the Oracle Cloud Infrastructure documentation

To ensure that a migrated service instance has the same performance characteristics as the original instance, and can support an equivalent workload, choose Oracle Cloud Infrastructure shapes that most closely map to the Oracle Cloud Infrastructure Classic shapes that you specified when you created the instance.

You must also confirm that the chosen shapes are available in your Oracle Cloud tenancy. Oracle configures shape limits for an Oracle Cloud Infrastructure region, or for a specific availability domain within a region. You can use the console to view the current shape limits for your tenancy, and to request a limit increase if necessary. See Service Limits in the Oracle Cloud Infrastructure documentation.