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

Your API Connect instance must use the top-level CR. Direct migration of individual API Connect subsystem installations to Cloud Pak for Integration by the steps described here is not supported. Alternative methods of migration if you are not using the top-level CR are:

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 Backing up, restoring, and disaster recovery. 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

Procedure

Update your <TOP_CR_NAME>-mgmt-admin-pass secret with your current Cloud Manager admin password:
1. Check whether the <TOP_CR_NAME>-mgmt-admin-pass password already matches your Cloud Manager admin password with:
```
oc get secret -n <APIC-namespace> | grep mgmt-admin-pass

oc get secret -n <APIC-namespace> <secret_name_from_previous command> -o jsonpath="{.data.password}" | base64 -d && echo ""
```
  If the passwords match then skip to 2.
2. From where you run OpenShift CLI commands, use the base64 command to encode your Cloud Manager admin password.
```
echo -n '<password>' | base64
```
  Note: If the base64 command is not available, alternative commands or tools can be used.
3. Edit the <TOP_CR_NAME>-mgmt-admin-pass secret:
```
oc edit secret <TOP_CR_NAME>-mgmt-admin-pass -n <namespace>
```
4. Replace the data.password value with your base64 encoded value from 1.b.
```
...
data:
  email: ZXhhbXBsZUBleGFtcGxlLmNvbQ==
  password: <base64 encoded password>
kind: Secret
metadata:
...
```
Note: The password in <TOP_CR_NAME>-mgmt-admin-pass is only used on API Connect installation, form factor migration, and disaster recovery. It does not need to be kept in sync with the Cloud Manager during normal API Connect usage.
Install IBM Cloud Pak Platform UI and create an instance of it.
Restart the apiconnect operator pod.

The restarted operator pod detects Cloud Pak for Integration and reconciles the subsystems with it. Wait for the subsystems to be healthy.
Log in to Cloud Manager and check the services under the topology section.

Known issue: If you see an additional Analytics service with a different name for the same Analytics endpoint, you must delete the newly created Analytics service.
Check that the configurator job is complete: :
```
oc get pods -n <namespace>
...
NAME                                                READY   STATUS      RESTARTS   AGE
<instance name>-configurator-<random string>        0/1     Completed   0          2h
...
```
Complete the following validation checks:
- Verify you are able to login to the Cloud Pak for Integration Platform UI, and can see your API Connect instance.
- Verify you are able to login to Cloud Manager UI, API Manager UI, and your portal sites.
- Test that your APIs are running, and analytics data is logged.
- Test lifecycle operations such as a product publish or delete, or an app creation.