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

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+ tool for clusters that are deployed in a single data center. You can also migrate multiple data centers to a multizone region. VPC+ 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+ 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+ 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+ tool.
  2. Add your classic and VPC accounts. When you add your VPC account, make sure to provide the Access Key ID and Secret Access Key, which are required to migrate your cluster.
  3. Select the Migrate Infrastructure option in the VPC+ Cloud Migration interface, and click Discover.
  4. Select your IBM Cloud classic account, and then click Create VPC Migration Workspace.
  5. You can now select the resource group, region, and zone where you want to migrate in VPC and the IBM Cloud Kubernetes Service or Red Hat OpenShift cluster that needs to be migrated.
  6. 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.
  7. After you select the appropriate resources and components, you can migrate your cluster to VPC.
  8. 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.