Migrating from OpenShift to Cloud Pak for Integration on the same cluster
Migrate your API Connect v10 deployment from OpenShift to Cloud Pak for Integration, while remaining on the same cluster.
Before you begin
- If the same subsystem endpoints can be used, deploy a new top-level CR API Connect and restore disaster recovery backups from your existing installation, see Disaster recovery on OpenShift and Cloud Pak for Integration. The new top-level CR deployment can then be migrated to Cloud Pak for Integration following the steps here.
- If different subsystem endpoints need to be used, migrate your API Connect deployment to a new top-level CR OpenShift cluster first. Follow the form factor migration steps Migrating from v10 to v10 on a different form factor, and then return here to complete the OpenShift top-level CR to Cloud Pak for Integration migration.
About this task
Migration from OpenShift to Cloud Pak for Integration on the same cluster results in
changes to the Management subsystem API endpoint URIs, as shown in these examples.
- apiManager endpoint changes from
tohttps://topcr-mgmt-api-manager-apic.example.com/manager
https://cpd-apic.example.com/integration/apis/apic/topcr/manager
- cloudManager endpoint changes from
tohttps://topcr-mgmt-admin-apic.example.com/admin
https://cpd-apic.example.com/integration/apis/apic/topcr/admin
- platformAPI endpoint changes from
tohttps://topcr-mgmt-platform-api-apic.example.com/
https://cpd-apic.example.com/integration/apis/apic/topcr/api
- consumerAPI endpoint changes from
tohttps://topcr-mgmt-consumer-api-apic.example.com/
https://cpd-apic.example.com/integration/apis/apic/topcr/consumer-api