Installing a two data center deployment on OpenShift

How to deploy a two data center disaster recovery (2DCDR) deployment on OpenShift.

Introduction

Ensure that you understand the concepts of 2DCDR in API Connect. For more information, see Two data center warm-standby deployment on Kubernetes and OpenShift.

Familiarize yourself with the OpenShift installation instructions linked from Deploying on OpenShift and Cloud Pak for Integration.

Note: 2DCDR is not supported on OpenShift where the top-level CR is used. For 2DCDR on OpenShift, you must install API Connect as individual subsystems. See Installing API Connect in a single namespace on OpenShift and Installing API Connect subsystems in different namespaces or environments on OpenShift.

Prerequisites

The prerequisites for a 2DCDR deployment on OpenShift are as follows.

  • The management and portal endpoints must be the same on both data centers.
  • The network latency between data centers must be no more than 80 ms.
  • The management cluster in each data center must use the same encryption secret.
  • The portal cluster in each data center must use the same encryption secret.
  • The ingress-ca certificate must be the same on both data centers.
Restrictions:

Enabling 2DCDR environment on API Agent

To enable the 2DCDR environment on API Agent, you need to enable active node deployment first, wait until the management node is ready, then enable the passive node deployment. If you have enabled the passive node instead of active, see Troubleshooting to resolve the issue.