Navigation

Overview

The beta release of the multi-Kubernetes-cluster deployments enables different levels of resilience, depending on the needs of your enterprise application:

  • Single Region, Multi AZ. One or more Kubernetes clusters where you deploy each cluster’s nodes in different zones in the same region. Such deployments protect MongoDB instances backing your enterprise applications against zone and Kubernetes cluster failures and offer increased availability, disaster recovery, and data distribution within one cloud region.
  • Multi Region. One or more Kubernetes clusters where you deploy each cluster in a different region, and within each region, deploy cluster nodes in different availability zones. This gives your database resilience against the loss of a Kubernetes cluster, a zone, or an entire cloud region.

Multi-Kubernetes-cluster deployments allow you to add MongoDB instances in global clusters that span multiple geographic regions for increased availability and global distribution of data.

The following diagram shows the high-level architecture of a multi-Kubernetes-cluster deployment across regions and availability zones. To learn more, see :ref: multi-cluster-arch-ref.

Diagram showing the high-level architecture of a multi-cluster-Kubernetes deployment across regions and availability zones using the MongoDB Enterprise Kubernetes Operator

Note

We recommend that you use a service mesh to enable inter-cluster communication between the replica set members deployed in different Kubernetes clusters. MongoDB development has tested this feature using Istio, but any service mesh that provides FQDN resolution between Pods across clusters should work.