Removing a two data center deployment

You can remove your two data center disaster recovery deployment on Kubernetes and OpenShift.

Before you begin

Ensure that you understand the concepts of two data center disaster recovery in API Connect. For more information, see A two data center deployment strategy on Kubernetes and OpenShift.

About this task

If you decide to remove your two data center disaster recovery (DR) deployment, you go from two data centers to one. The active data center remains as the only working system. The passive one loses all data as part of the process.

Warning: If the active data center is offline, do not remove the multi-site HA CR section from the passive data center, as this action deletes all the data from the databases.

As part of the installation, you included a multiSiteHA configuration section in each data center. For example:

siteName: dallas
multiSiteHA:
  mode: active
  replicationEndpoint:
    annotations:
      cert-manager.io/issuer: ingress-issuer
    hosts:
    - name: ptlreplicationdallas.cluster1.example.com
      secretName: dallas-ptl-replication-worker-1
  replicationPeerFQDN: ptlreplicationraleigh.cluster2.example.com
  tlsClient:
    secretName: ptl-replication-client
...

siteName: raleigh
multiSiteHA:
  mode: passive
  replicationEndpoint:
    annotations:
      cert-manager.io/issuer: ingress-issuer
    hosts:
    - name: ptlreplicationraleigh.cluster2.example.com
      secretName: raleigh-ptl-replication-worker-1
  replicationPeerFQDN: ptlreplicationdallas.cluster1.example.com
  tlsClient:
    secretName: ptl-replication-client
...

If you want to revert to a single data center topology, or temporarily remove the passive data center from DR, you must remove the multi-site HA CR section from the active data center, and then redeploy the passive data center. If the active data center is offline, you must first change the passive data center to be active, and then remove the multi-site HA CR section from the now active data center.

Procedure

Remove the multiSiteHA section from the Management and Portal subsystem CRs on the active data center.
Apply the updated CR files to the subsystems on the active data center, for example:
```
kubectl apply -f portal_cr.yaml -n <namespace>
```
```
kubectl apply -f management_cr.yaml -n <namespace>
```
Where <namespace> is the target installation namespace in the Kubernetes cluster for the active data center.
You must delete your passive data center. For more information, see Uninstalling API Connect.