Deploying an API Connect cluster or subsystems on s390x

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

Before you begin

The following limitations apply to this deployment:

The 2 data center deployment configuration is not supported.
You can't customize internal certificates.

Deployment procedure

Deploy the API Manager and API Portal subsystems on the s390x cluster. Do one of the following:
- Deploy an instance of an API Connect cluster on the Platform UI. For more information, see Deploying an instance by using the Platform UI.
- Deploy the API Manager and API Portal subsystems by using the CLI. For more information, see Deploying the API Manager 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 an amd64 cluster. For more information, see Deploying the API Gateway subsystem by using the CLI.
Deploy the API Analytics subsystem on an amd64 cluster. For more information, see Deploying the API Analytics subsystem by using the CLI.

Copying the ingress issuer certificates to the amd64 cluster

After you deploy the API Manager and API Portal subsystems on the s390x 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 s390x 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 s390x cluster where the API Manager subsystem is running. Run the following command on the s390x 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
```
Important: If you intend to deploy the API Gateway and API Analytics subsystems to different namespaces, then repeat steps 3-6 in each target namespace.
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