mongot Deployment Limitations

Sharded cluster topologies that the MongoDB Controllers for Kubernetes Operator manages are supported for MongoDB Enterprise Advanced only. To learn which topologies the MongoDB Controllers for Kubernetes Operator supports, see Supported Topologies.

A mongot instance is bound to a single replica set, or to a single shard in a sharded cluster. You cannot share one mongot instance across multiple mongod deployments. Deploy a separate mongot instance for each replica set or shard.

A self-managed load balancer only supports single-cluster deployments. Multi-cluster deployments require the managed Envoy load balancer.

mongot does not support cross-cluster query failover. Each cluster's search deployment is independent. If a cluster becomes unavailable, search is unavailable in that cluster, and queries do not fail over to another cluster.

When you delete a multi-cluster MongoDBSearch resource, Kubernetes garbage collection removes only the resources in the central cluster. The MongoDB Controllers for Kubernetes Operator does not delete the mongot resources that it created in the other member clusters. Delete those resources manually.

If you remove a cluster from spec.clusters, the MongoDB Controllers for Kubernetes Operator does not remove all of that cluster's resources.

• For sharded cluster sources, the MongoDB Controllers for Kubernetes Operator removes the stale mongot StatefulSets, Services, and ConfigMaps, but does not remove the TLS certificate Secrets or the Envoy proxy resources.

• For replica set sources, the MongoDB Controllers for Kubernetes Operator does not remove any of the cluster's resources. Delete the remaining resources manually.

mongot reads certificates at startup and does not reload them while running. If you rotate the TLS certificate in the Secret that spec.security.tls.certsSecretPrefix references, the MongoDB Controllers for Kubernetes Operator detects the change and restarts mongot automatically in a rolling fashion, one mongot pod at a time in each mongot group.

mongot reads credentials at startup. After you rotate the SCRAM password for the search-sync-source user, you must restart mongot so that it reads the new credentials. The MongoDB Controllers for Kubernetes Operator does not restart mongot automatically for this change.

mongot does not validate OCSP or CRL certificate revocation. To reject a revoked certificate, remove the corresponding $external user on mongod.

mongot does not provide application-level encryption at rest. To encrypt the mongot index data, encrypt the underlying volume with a Kubernetes-level or cloud-provider mechanism. To learn more, see Secure the Connection from MongoDB to Search.

mongot reads its configuration at startup and does not support live configuration reload. If you change the MongoDBSearch resource, the MongoDB Controllers for Kubernetes Operator restarts mongot automatically in a rolling fashion, one mongot pod at a time in each mongot group, to apply the change.

mongot upgrades require a process restart. No in-place binary swap is supported. To learn more, see Upgrade or Downgrade.

Index storage is not portable across mongot major versions. A mongot major-version downgrade requires a re-sync, which rebuilds the index from the source data. Plan major-version upgrades carefully and back up mongod so that the index can be rebuilt if you need to downgrade.

The Metrics UI in Atlas is not available for mongot deployments that you manage yourself. To set up monitoring, use the metrics endpoint that mongot exposes, or forward mongot metrics to Ops Manager with the metrics forwarder. The metrics forwarder requires Ops Manager 8.0.25 or later and does not support Cloud Manager. To learn more, see Monitor Your Deployment.

Automated embedding is a Preview feature and integrates only with Voyage AI models. To use another embedding provider, generate embeddings in your application and store them in a vector field.

Automated embedding is only available for single-cluster topologies.

Features that are guarded by Atlas-only flags are not available on self-managed mongot. A feature is available on self-managed deployments only after it ships in a mongot binary release.

Troubleshoot mongot Deployment

Supported Topologies