No host described in new configuration with maps to this node

[dobesv]

Report

Trying to get up and running with a new cluster, it seems I have somehow gotten past the prior issue but now it complains that the replica list it is provided in invalid. I think the issue might be that the replica information it is provided has the node's IP address in it instead of the pod's.

More about the problem

{"t":{"$date":"2025-06-27T23:43:03.860+00:00"},"s":"E",  "c":"REPL",     "id":21425,   "ctx":"ReplCoord-0","msg":"replSetInitiate error while validating config","attr":{"error":{"code":74,"codeName":"NodeNotFound","errmsg":"No host described in new configuration with {version: 1, term: 0} for replica set rs-stagingdb-0 maps to this node"},"config":{"_id":"rs-stagingdb-0","version":1,"members":[{"_id":0,"host":"172.22.68.243:31623","arbiterOnly":false,"buildIndexes":true,"hidden":false,"priority":2,"tags":{"nodeName":"i-0215d5a003c7459f1","podName":"stagingdb-rs-stagingdb-0-0","serviceName":"stagingdb"},"votes":1}]}}}

Pod IP is 100.109.142.143 and node IPs are InternalIP: 172.22.68.243 ExternalIP: 18.208.207.220

Steps to reproduce

Versions

1. Kubernetes v1.30.12
2. Operator v1.20.1
3. Database mongodb

Anything else?

Likely this is caused by some mistake we have made, but the operator isn't doing a good job of detecting and reporting that mistake.

[hors]

Hi @dobesv, could you please share your CR with me? I will try to reproduce it.

[dobesv]

Ah, sorry, I've gone through many iterations since then and I don't have it now. I've disabled expose and I created some NLB services manually. Are you able to expose a cluster using NodePort and NOT get this issue?

If exposing via NodePort works in general, it might be due to me not having setup a sepeatate -ssl-internal certificate/secret at the time.

[dobesv]

Here's my current CR YAML: https://gist.github.com/dobesv/c2727a9ee382ce80638d61bd0d64ca30

You could imagine this one, but trying to expose it using NodePort.

[egegunes]

@nmarukovich please try to reproduce this issue.

[nmarukovich]

Could you please share CR with nodePorts settings that you tried to use.
For main branch with k8s version v1.31.12 I can run cluster and can't see any error.