hi @Pavel_Duchovny confirmed that the config does include the bind address:
I have no name!@customer-replica-set-0:/$ more /data/automation-mongod.conf
net:
bindIp: 0.0.0.0
port: 27017
tls:
CAFile: /mongodb-automation/ca.pem
allowConnectionsWithoutCertificates: true
certificateKeyFile: /mongodb-automation/server.pem
mode: allowTLS
processManagement:
fork: “true”
replication:
replSetName: customer-replica-set
storage:
dbPath: /data
engine: wiredTiger
systemLog:
destination: file
path: /var/log/mongodb-mms-automation/mongodb.log
Regarding VPC and host resloution yes it is enabled since I can get to the OPS manager and by test nginx pod with nodeport test.
Primary Mongod log during a failed attempt, I did provide this earlier from the client side. I don’t think there is going to be anything at the pod level since the traffic is not even getting thru. If there is anything specific you need let me know where to find and upload it here.
I will be tearing down the cluster in the interest of cost but if you do get through the test let me know what you find. I can certainly repeat this issue repeatedly and can spin up a cluster any time we need to try this again but I believe this is an issue with Operator and DNS resolution within the cluster or how the replicasethorizons is set.
Thanks @Pavel_Duchovny for staying with me.