Cannot connect to ReplicaSet from within Kubernetes Cluster about mongodb-kubernetes-operator HOT 7 CLOSED

So today I've tried to isolate the issue by creating a minimal reproduction. It turned out, that everything works fine.
Honestly, I don't know where the issue was, but now it works 🤣

You can check it out here: https://github.com/flolu/mongodb-k8s-connection

from mongodb-kubernetes-operator.

@StMarian Yes. I've deployed it into the mongodb namespace, but nevertheless I get the error mentioned above.

from mongodb-kubernetes-operator.

I think the problem is in your connection string:
mongodb://event-store-svc.mongodb.svc.cluster.local:27017 - this is the format of the connection string to the single instance of mongodb
if you want to connect to the replicaset, your connection string should look like this:
mongodb://event-store-0.event-store-svc.mongodb.svc.cluster.local:27017,event-store-1.event-store-svc.mongodb.svc.cluster.local:27017/?replicaSet=event-store

source: https://docs.mongodb.com/manual/reference/connection-string/#replica-set-option
k8s pod dns name: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-aaaa-records-1

from mongodb-kubernetes-operator.

@StMarian I've tried the new connection string, but unfortunately, I still get this error:

MongoServerSelectionError: connect ECONNREFUSED 10.1.74.34:27017
    at Timeout._onTimeout (node_modules/mongodb/lib/core/sdam/topology.js:430:30)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7)

Do you have any other idea, what might be the reason for this error?

from mongodb-kubernetes-operator.

@StMarian I also face the same issue.

I tried with

mongodb://example-mongodb-0.example-mongodb-svc.mongodb.svc.cluster.local:27017,example-mongodb-1.example-mongodb-svc.mongodb.svc.cluster.local:27017/?replicaSet=example-mongodb

Error log:
node:1) UnhandledPromiseRejectionWarning: MongoNetworkError: failed to connect to server [example-mongodb-1.example-mongodb-svc.mongodb.svc.cluster.local:27017] on first connect [Error: getaddrinfo ENOTFOUND example-mongodb-1.example-mongodb-svc.mongodb.svc.cluster.local at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:66:26) { name: 'MongoNetworkError', [Symbol(mongoErrorContextSymbol)]: {} }] at Pool.<anonymous> (/app/node_modules/mongodb/lib/core/topologies/server.js:433:11) at Pool.emit (events.js:315:20) at /app/node_modules/mongodb/lib/core/connection/pool.js:577:14 at /app/node_modules/mongodb/lib/core/connection/pool.js:1021:9 at /app/node_modules/mongodb/lib/core/connection/connect.js:31:7 at callback (/app/node_modules/mongodb/lib/core/connection/connect.js:247:5) at Socket.<anonymous> (/app/node_modules/mongodb/lib/core/connection/connect.js:276:7) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:84:8)

from mongodb-kubernetes-operator.

@flolu, @jamesbroadhead the connection string that I provided assumes that the mongodb is deployed to the mongodb namespace. If this is not true, you will need to update the connection string and use the correct namespace:
mongodb://event-store-0.event-store-svc.mongodb.svc.cluster.local:27017,event-store-1.event-store-svc.mongodb.svc.cluster.local:27017/?replicaSet=event-store

from mongodb-kubernetes-operator.

I guess the issue is with the connection string. Hope this can be documented in the readme file. Thanks in advance.

from mongodb-kubernetes-operator.