If you use MongoDB Search or Vector Search with the deployment that you are migrating, review this page before you begin. Kubernetes Operator handles a MongoDBSearch resource differently depending on whether the MongoDB resource it attaches to uses externalDomain.
externalDomain Is Not Supported
MongoDBSearch does not support MongoDB resources that use spec.externalAccess.externalDomain. If your migration plan depends on setting externalDomain for network
requirements, and you also use MongoDB Search or Vector Search against this deployment, do not set externalDomain on the MongoDB resource you migrate into. Use plain spec.externalAccess (without externalDomain) to expose Kubernetes Pods to your virtual machines instead.
Keep MongoDBSearch on the External Source
To keep a MongoDBSearch resource attached to the deployment throughout the migration, continue using spec.source.external.hostAndPorts rather than switching to spec.source.mongodbResourceRef. As you extend the deployment into Kubernetes and prune virtual machine members, manually edit spec.source.external.hostAndPorts to add the hostnames of the new Kubernetes-hosted mongod Pods so the seed list stays current.
For the full field reference, see MongoDBSearch Resource Specification.
Automatic additionalMongodConfig Population
The kubectl mongodb migrate-to-mck plugin automatically populates spec.additionalMongodConfig on the generated MongoDB resource with the values that mongot needs to connect. Verify these values before you apply the generated MongoDB resource.