Thanks @Dan_Mckean Appreciate your help. I tried to make use of the keyFile from K8s deployment in EC2 mongodb instance & sync the authentication process as well, however with this approach, the authentication is successful, but getting a replicaset ID mismatch.
lastHeartbeatMessage: "replica set IDs do not match, ours: 65cdafd3d2xxxxxxxx; remote node's: 65cda23ea90xxxxxxxxxxxxx",.
Tried the mongosync approach - executing the mongosync from EC2 mongodb, however, the mongosync is unable to connect to the EKS mongodb which is exposed via a nodeport. I guess its because of internal replica is named in K8s DNS i.e <namespace>.<service>.svc.cluster.local:27017. Does a rs.reconfig works here ?
Does the MongoDB enterprise supports Hybrid Replication between K8s and VM based deployment ? Kindly advice. Thanks!