For AI agents: a documentation index is available at https://www.mongodb.com/docs/llms.txt — markdown versions of all pages are available by appending .md to any URL path.
Docs Menu

Supported Topologies

You can deploy MongoDB Search and Vector Search with the Kubernetes Operator against a range of MongoDB deployment topologies. The topology that you choose determines how the Kubernetes Operator deploys and connects the mongot process to your MongoDB deployment.

Use this page to confirm that your planned topology is supported before you deploy. To confirm the MongoDB Server, mongot, and Kubernetes Operator versions that you need, see Search and Vector Search Compatibility and Requirements.

A supported topology is a combination of the following dimensions:

  • MongoDB Cluster topology. Whether the mongot process serves a MongoDB replica set or a sharded cluster. For sharded clusters, the Kubernetes Operator deploys a separate mongot group for each shard.

  • Load balancer mode. When you run multiple mongot instances, you must place an L7 load balancer between mongod and the mongot pods. You can use one of the following options:

    • Managed load balancer. The Kubernetes Operator deploys and configures an Envoy proxy.

    • Unmanaged load balancer. You provide and configure your own L7 load balancer.

    A single mongot instance connects directly to mongod and does not require a load balancer.

  • MongoDB deployment. Whether the Kubernetes Operator manages the MongoDB deployment inside Kubernetes (managed) or the mongot process connects to a MongoDB deployment that runs outside Kubernetes (external).

The following table lists the support status for each combination of deployment dimensions:

Important

External MongoDB deployments require MongoDB Enterprise. MongoDB Community supports only replica set deployments that the Kubernetes Operator manages inside Kubernetes.

Cluster Topology
Load Balancer Mode
MongoDB Deployment
Support Status

Replica set

Managed

Managed

Supported

Replica set

Managed

External

Supported

Replica set

Unmanaged

Managed

Supported

Replica set

Unmanaged

External

Supported

Sharded cluster

Managed

Managed

Supported

Sharded cluster

Managed

External

Supported

Sharded cluster

Unmanaged

Managed

Supported

Sharded cluster

Unmanaged

External

Supported

Review the following considerations when you choose a topology:

  • External MongoDB deployments are available only for MongoDB Enterprise. MongoDB Community supports replica set deployments that the Kubernetes Operator manages inside Kubernetes.

For other deployment limitations, see mongot Deployment Limitations.