Migration wizard quickstart guide
Classic infrastructure
Use the migration wizard to migrate a Classic cluster to VPC in a guided, end-to-end workflow from the IBM Cloud console.
This quickstart shows you how to open the migration wizard and what to expect in each step. For a full explanation of each step, see Migrating from Classic to VPC.
Before you begin
Make sure that you have the following items.
- A Classic cluster. To check, go to Containers > Clusters in the IBM Cloud console and confirm that at least one cluster shows Classic as the infrastructure type.
- At least the Operator (
containers-kubernetes.cluster.operate) IBM Cloud® Identity and Access Management platform access role for Red Hat OpenShift on IBM Cloud on both the Classic cluster and the VPC cluster. See Assigning cluster access. - An IBM Cloud Object Storage (COS) instance in the same account. The migration service uses COS to store generated metadata and migration plans.
- An IBM Cloud Backup and Recovery Service (BRS) instance in the same account as your Classic cluster. The BRS instance can be in any resource group in that account. BRS is required to migrate workload and storage data.
- Access your Red Hat OpenShift cluster.
Step 1: Open the migration wizard
You can open the migration wizard from the Migration hub or from the Containers page. Choose the entry point that you prefer.
Open the wizard from the Migration hub
- Go to Migration hub.
- Click the Clusters tile, or use the navigation to go to Clusters.
- Open Eligible clusters.
- Find your Classic cluster and click Open wizard.
Open the wizard from the Containers page
- Go to Containers > Clusters.
- In the row actions for your Classic cluster, select Migrate to VPC.
The wizard opens on the Migrating CLUSTER_NAME page. The left navigation panel shows your progress through each step.
Step 2: Follow the migration wizard
Complete the wizard steps in order. The steps in the following table match the steps in the migration wizard.
| Phase | Step | What you do |
|---|---|---|
| Phase 1 | Step 1: Assess | Select a COS instance, run the assessment, and review the proposed VPC configuration. |
| Phase 1 | Step 2: Create | Provision the VPC cluster. Infrastructure migration starts automatically. |
| Phase 1 | Step 3: Migrate | Choose a backup and recovery instance, create migration plans, and move workloads to the VPC cluster, namespace by namespace. |
| Phase 2 | Cutover | Redirect DNS traffic to the VPC cluster, validate your workloads, and complete the finish migration checklist. |
Cutover and deleting the Classic cluster are manual processes. The migration wizard does not do them for you.
Next steps
- Assess your Classic cluster and generate the VPC configuration metadata.
- Review what is and is not migrated automatically before you start.
- Prepare for cutover by reading Cut over and validate.