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

Search and Vector Search Compatibility and Requirements

This page describes the version compatibility and minimum component requirements for running MongoDB Search and Vector Search with the MongoDB Controllers for Kubernetes Operator. Use it to ensure that your planned deployment meets the requirements before you deploy mongot.

To deploy MongoDB Search and Vector Search, you must run the following component versions or later:

Component
Minimum version

MongoDB Server

8.3.4

mongot

1.70.1

MongoDB Controllers for Kubernetes Operator

1.9.1

Ops Manager or Cloud Manager

Latest (Enterprise deployments only; not used by Community)

You can run newer versions of any component if the combinations remain within the supported pairings described in the following sections.

Any supported mongot version is compatible with any supported mongod version of MongoDB Server 8.3.4 or later. Concretely:

  • mongot 1.70.1 works with mongod 8.3.x.

  • Features added in newer mongot might require a newer mongod to function. They are surfaced through clear error messages, but there might also be silent failures.

  • Existing features keep working when mongot is upgraded without upgrading mongod, and vice versa.

This allows you to upgrade mongot and mongod independently rather than coordinating both in the same maintenance window.

The Kubernetes Operator declares the mongot versions it supports. Use the Kubernetes Operator version that ships alongside or after the mongot version you intend to deploy. To learn more, see MongoDB Controllers for Kubernetes Operator Compatibility.

MongoDB Search and Vector Search on Kubernetes inherit the platform support of the MongoDB Controllers for Kubernetes Operator. Confirm that your cluster meets the Kubernetes Operator requirements before you deploy mongot:

You can run MongoDB Search and Vector Search against either edition of MongoDB Server that the Kubernetes Operator manages:

  • Community Edition: Manage the source mongod through the MongoDBCommunity resource. Ops Manager and Cloud Manager do not apply in this configuration.

  • Enterprise Edition: Manage the source mongod through the MongoDB resource, paired with Ops Manager or Cloud Manager.

Both editions use the same MongoDBSearch resource to deploy mongot. For a deployment that is external to the Kubernetes Operator, reference it through spec.source.external on the MongoDBSearch resource. To learn more, see MongoDB Search and Vector Search Settings.