Skip to content

fix: when running minikube, don't add replicaSet

Keith Grootboom requested to merge keith/minikube-patches into main

Description

Fixes the MongoDB error when trying to run Grove the minikube provider.

The default MongoDB deployed with Grove doesn't work, because it's trying to connect to a replicaSet, which doesn't exist.

This PR fixes it by disabling the replicaSet if it's not defined.

In particular it fixes the below error when running with minikube

pymongo.errors.ServerSelectionTimeoutError: client is configured to connect to a replica set named '' but this node belongs to a set named 'None', Timeout: 30s, Topology Description: <TopologyDescription id: 62f3b1d52f38765da75a91c1, topology_type: Single, servers: [<ServerDescription ('mongodb', 27017) server_type: Unknown, rtt: None, error=ConfigurationError("client is configured to connect to a replica set named '' but this node belongs to a set named 'None'")>]>

Testing instructions

  • Deploy with minikube. You won't get the above error.
Edited by Keith Grootboom

Merge request reports