Free5gc NRF is waiting for MongoDB indefinitely about towards5gs-helm

[Zhenye-Na]

Closed this issue since it is not related to specific helm chart implementation.

For anyone who is curious, this issue is related to DNS lookup issue that is similar to aws/aws-cdk#10884

[Zhenye-Na]

Added more findings:

It seems like the NRF chart works when:

1. AWS EKS Cluster has only instances coming from EKS Managed Node Group
2. AWS EKS Cluster has only instances coming from EKS Self-managed Node Group

If there are multiple instances, and the source of them is mix-matching. The NRF helm chart is installed and MongoDB is running, the wait-mongo container of NRF could not find the the Mongo pods, with same logs found above

kubectl logs nrf-free5gc-nrf-nrf-79d7d9b788-cmghx -c wait-mongo
nc: bad address 'mongodb:27017'
waiting for the MongoDB
nc: bad address 'mongodb:27017'
waiting for the MongoDB

In AWS EKS Console, I am able to see that mongodb-0 and nrf-free5gc-nrf-nrf-79d7d9b788-cmghx are installed in the same EC2 instances, resources such as memory, total number of pods or IPs are not running up.

So I would really appreciate it if any tips or findings can be provided.

Thanks!!