Thanks for getting back to me with that information and the
The SRV record has a reference to these shard names. By specifying mongodb+srv:// in the connection string, I am telling the driver to please use the SRV record. Hence, the URI that comes after that is the SRV record. Is my understanding correct?
Yes, your understanding here is correct. However, the shard names you are referencing are specific to Sharded Clusters. The SRV record references the hostnames of the nodes within your cluster. Since you’ve mentioned this is an M10 cluster, I would assume that this is a standard replica set and not a sharded cluster.
So by performing the connection this way, and I used the private connection (you can see the -pri in the name above), this means all my connectivity is flowing via the VPC peering that I have established. Is this correct?
Yes, this is also correct.
And during the installation of the components referenced by the helm chart, I am seeing connectivity failures to MongoDB. My tests in manually connecting to the Atlas instance was done using a pod deployed in the same K8 cluster, so I think network, and IP address whitelisting is sorted out.
It does sound like there is no network, Atlas configuration or cluster issues from your description at this stage. However, to better troubleshoot this would you be able to provide the full connectivity failure errors you’re receiving?