Red Hat OpenShift on VPC multiregion DR

Architecture diagram

Review the following containers, SDS, and backup disaster recovery components that corresponds with Figure 1:

1. Separate hyperconverged compute and storage Red Hat OpenShift clusters are created in primary and DR region accounting for containerized applications and environments that require disaster recovery protection.

   1. To meet the high availability 99.99% SLA 6 worker nodes equally distributed across three availability zones are included within each Red Hat OpenShift cluster in each region.

   2. A minimum of 3 worker nodes with extra local block storage is required so that the Portworx built-in internal key-value database (KVDB) can be set up for high availability. The KVDB stores the state, configuration data, and metadata for your cluster. Your data is automatically replicated across these 3 worker nodes, and you can choose to scale this deployment to replicate data across up to 25 worker nodes.

2. Portworx Enterprise DR provides data replication between Red Hat OpenShift source and failover destination clusters in separate regions. Each cluster has its own Portworx Enterprise DR installation and uses a separate Portworx key-value store that is not shared.

3. Block Storage for VPC is used as the backing storage for Portworx Enterprise DR and volumes are provisioned on a per availability zone basis.

4. Portworx Enterprise DR async replication is used between the primary and DR site for the DR data replica.

   1. Setting up disaster recovery with Portworx

5. Portworx Backup is used to backup up cluster resources applications and data from target and source application clusters. Choose the cluster where Portworx Backup is to be installed (this cluster can also be backed up).

6. Add the Red Hat OpenShift clusters that will be backed up to the Portworx Backup service.

7. An IBM Cloud Object Storage instance and bucket is used as the backup location to the Portworx Backup service.

8. Cross-region COS plan is used for multiregional protection with concurrent access to protect against entire regional unavailability or outage.

9. To back up a cluster without Portworx Enterprise, you must first install the Portworx storage scheduler Stork before you add the cluster to the Portworx Backup service.

10. Public connectivity: Cloud Internet Services (CIS) Global Load Balancer feature is used to provide public traffic load balancing between the primary and DR sites.

11. Public connectivity: VPN for VPC is used to provide secure connectivity from on-premises networks and admin access from anywhere.

12. Private connectivity: Redundant (or single) Direct Link connections that are established to the primary and DR sites with Transit Gateway connections.

13. Private connectivity: Global Routing is added to the DR region Direct Link for resilient private network connectivity outside the local market.

14. Private connectivity: Global Transit Gateway in the DR region provides interconnectivity between VPCs for replication traffic between IBM Cloud regions.

15. Private connectivity: Private DNS Services Global Load Balancer or customer provided GLB is used to provide private traffic load balancing between the primary and DR sites.

Design scope

Following the Architecture Design Framework, the Red Hat OpenShift Service on VPC DR pattern covers design considerations and architecture decisions for the following aspects and domains:

• Compute: Containers

• Storage: Primary storage, backup storage, software-defined storage

• Networking: Enterprise connectivity, load balancing, DNS

• Resiliency: Backup and restore, disaster recovery

The Architecture Design Framework provides a structured approach to designing cloud solutions by covering key architectural aspects and domains, helping ensure consistency across enterprise solutions regardless of technology. For more information, see Introduction to the Architecture Design Framework.

Requirements

The following table outlines key baseline requirements that are essential for most clients to successfully deploy the Red Hat OpenShift Service on VPC DR pattern.

Solution components