Migrating classic IBM Cloud Kubernetes Service or Red Hat OpenShift cluster to VPC

You can migrate your classic IBM Cloud® Kubernetes Service or Red Hat® OpenShift® cluster to VPC by using the VPC+ Cloud Migration tool for clusters that are deployed in a single data center. You can also migrate multiple data centers to a multizone region. VPC+ Cloud Migration discovers both the classic and IBM Cloud Kubernetes Service or Red Hat OpenShift resources and components. Along with the other resources and workloads running within Kubernetes, see the following list for some of the components and resources that are discovered:

  • Worker nodes and pools
  • PODs
  • Namespaces
  • Secrets
  • StatefulSets
  • DaemonSet
  • Deployments
  • ConfigMaps
  • Custom resource definitions
  • PVC

As part of the migration, the VPC+ Cloud Migration tool creates a new cluster in a VPC single availability zone, and backs up and restores the Kubernetes workload resources to your new VPC environment.

Before you begin

Before you begin migrating your classic IBM Cloud Kubernetes Service or Red Hat OpenShift cluster to VPC by using the VPC+ Cloud Migration tool, review the following requirements:

  1. Be familiar with the Considerations for IBM Cloud Kubernetes Service and Red Hat OpenShift migration.
  2. Make sure that the IBM Cloud Kubernetes Service or Red Hat OpenShift Administrator role is assigned to your user account.
  3. You need both a classic infrastructure API key and IBM Cloud VPC API key.
  4. HMAC keys (Access Key ID and Secret Access Key) are required when you add a VPC account for workload backup and restore.

Limitations

Review the following limitations:

  • Private clusters cannot be migrated.
  • Only PVC with block storage is supported.
  • For any services that rely on IPs, the IPs must be updated post-migration (for example, DNS, load balancers, security rules, etc.).

Migrating to VPC

  1. Log in to the VPC+ Cloud Migration tool.
  2. Add your classic and VPC accounts.
  3. Select the Manage VPCs option in the VPC+ Cloud Migration interface, and click IBM Cloud.
  4. Select your IBM VPC, and then select any destination Region.
  5. Click on the Kubernates Cluster and then click on Migrate Cluster.
  6. Select the Migrate Infrastructure option in the VPC+ Cloud Migration interface, and click Discover.
  7. Select the Classic Cloud account and click on the discover clusers. Once discovery is completed, select the cluster which one you want to migrate. After that choose the option to migrate the cluster in the existing VPC or create a new VPC.
  8. You can now select the resource group where you want to migrate in VPC (Provide VPC name incase of creating new VPC), Cloud Object Storage, Bucket (Where the data will be stored) Cloud Object Storage Creds (An access key with HMAC value as true and manager role is required for migration).
  9. Review the requirements and considerations for the following components:
    • Address prefix - Classic address prefixes are not supported in VPC. Make sure to create a new address prefix and enable the public gateway.
    • IBM Cloud Kubernetes Service or Red Hat OpenShift cluster name - The cluster name must be a new and unique.
    • Worker nodes - Classic worker pool flavors are not supported in VPC. Should be updated with available VPC flavour.
  10. After you select the appropriate resources and components, you can migrate your cluster to VPC.
  11. After you migrate your clusters, verify and validate the clusters. You might need to do some fixes or redeployments on the migrated clusters, especially for Red Hat OpenShift clusters if you are using tooling specific to Red Hat OpenShift, such as internal image registry or operators.

To learn more about the process:

  • Log in to wanclouds VPC+ Cloud Migration.
  • Navigate to Disaster Recovery.
  • Select Virtual Machine.
  • Click on Setup Backup Manager > Data Sync.
  • Follow the on-screen instructions to set up the agent and begin data migration.