Deploying an API Connect cluster or subsystems on ppc64le

To deploy an API Connect cluster on ppc64le, deploy the API Manager, API Analytics, and API Portal subsystems on ppc64le, and deploy the API Gateway subsystem on amd64.

Restriction: The following API Connect functionality is not currently available on ppc64le in Cloud Pak for Integration:

Two data center disaster recovery (although regular backup and restore and basic disaster recovery are supported)
Open Tracing for the API Connect cluster
API Discovery collectors (these are only supported on amd64)
IBM API Connect Test and Monitor, including AutoTest Assist
Customizing internal certificates

Deployment procedure

Deploy the API Manager, API Analytics, and API Portal subsystems on the ppc64le cluster. Do one of the following:
- Deploy an API Connect cluster instance on the Platform UI. For more information, see Deploying an instance by using the Platform UI.
- Deploy the API Manager, API Analytics, and API Portal subsystems by using the CLI. For more information, see Deploying the API Manager subsystem by using the CLI, Deploying the API Analytics subsystem by using the CLI, and Deploying the API Portal subsystem by using the CLI.
Copy the ingress issuers to the amd64 cluster by following the steps in the next section, "Copying the ingress issuers to the amd64 cluster".
Deploy the API Gateway subsystem on amd64. For more information, see Deploying the API Gateway subsystem by using the CLI.

Copying the ingress issuer certificates to the amd64 cluster

After you deploy the API Manager, API Analytics, and API Portal subsystems on the ppc64le cluster, export the ingress issuer certificates and copy them to the amd64 cluster. This process ensures that the subsystems you deploy next on the amd64 cluster can communicate with the subsystems on the ppc64le cluster.

Verify that the Cloud Pak for Integration and API Connect operators are installed on the amd64 cluster.
Export the API Manager ingress CA secret from the namespace of the ppc64le cluster where the API Manager subsystem is running. Run the following command on the ppc64le cluster, where <apiconnect_cluster_name> is the name of the API Connect cluster instance:
```
oc get secret <apiconnect_cluster_name>-ingress-ca -o json| jq 'del(.metadata.creationTimestamp,.metadata.namespace,.metadata.resourceVersion,.metadata.uid,.metadata.selfLink)' > ingress-secret.json
```
Apply ingress-secret.json to the target namespace on the amd64 cluster:
```
oc apply -f ingress-secret.json -n <namespace>
```

Create a file named ingress-issuer.yaml as in the following example. Replace <apiconnect_cluster_name> with the name of the API Connect cluster instance.

apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: <apiconnect_cluster_name>-ingress-issuer
spec:
  ca:
    secretName: <apiconnectCluster_name>-ingress-ca
---
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: <apiconnect-cluster_name>-self-signed
spec:
  selfSigned: {}

Apply the ingress-issuer.yaml to the target namespace on the amd64 cluster:
```
oc apply -f ingress-issuer.yaml -n <namespace>
```

Validate that the issuers are in the READY state by running the following command:

oc get issuer -n <namespace>

The response should be similar to the following example:

NAME                                      READY
my-api-connect-cluster-name-ingress-issuer   True
my-api-connect-cluster-name-self-signed      True