We have deployed percona operator for MongoDB with exposeType : clusterIP in our AKS . I have created another service with internal azure loadbalancer without modifying existing percona managed headless service and able to connect from percona-mongo-client from another pod within cluster.
Note: I have added routes to reach cluster to connect vaiaVPN.
So now i need to connect from outside of aks but having issues connecting to mongodb i.e., Starting new replica set monitor for rs/xx.xx.xx.xx:27017
2023-03-23T17:54:44.432+0530 I NETWORK [thread1] Successfully connected to 126.96.36.199:27017 (1 connections now open to xx.xx.xx.xx:27017 with a 5 second timeout)
2023-03-23T17:54:44.874+0530 I NETWORK [thread1] getaddrinfo(“percona-mongodb-db-ps-rs-1.percona-mongodb-db-ps-rs.mongodb.svc.cluster.local”) failed: Name or service not known
2023-03-23T17:54:45.399+0530 I NETWORK [thread1] getaddrinfo(“percona-mongodb-db-ps-rs-2.percona-mongodb-db-ps-rs.mongodb.svc.cluster.local”) failed: Name or service not known
2023-03-23T17:54:45.399+0530 I NETWORK [ReplicaSetMonitor-TaskExecutor-0] getaddrinfo(“percona-mongodb-db-ps-rs-0.percona-mongodb-db-ps-rs.mongodb.svc.cluster.local”) failed: Name or service not known
How do i resolve this issue?