Synchronous DR for Kubernetes

Portworx supports synchronous (Metro) DR when installed as a single stretch cluster across multiple Kubernetes clusters. The Kubernetes clusters need to span across a metropolitan area network with a maximum latency of 10 ms. This document explains how to install a stretch Portworx cluster and achieve synchronous DR. It will demonstrate how to failover and failback applications between two Kubernetes clusters.

Perform the following steps to set up Metro DR:

note

• The sections of this document require specifying a <namespace>, you should update this to the namespace where Portworx is installed in your environment.
• A maximum replication factor of 2 is supported in a Metro-DR deployment. Using repl: 3 might cause downtime because of a loss of volume quorum.

📄 Prerequisites

Prerequisites for Synchronous DR migration.

📄 Prepare your cluster

Find out how to install a single stretch Portworx cluster across multiple Kubernetes clusters.

📄 Generate and apply a cluster pair spec

Find out how to pair your clusters.

📄 Schedule a migration

Find out how to synchronize your clusters by scheduling periodic migrations between them.

📄 Configure reverse migration

Find out how to reverse synchronize your clusters..

📄 Failover an application

Find out how to failover an application from one Kubernetes cluster to another.

📄 Failback an application

Find out how to failback an application from the backup Kubernetes cluster to the original one.