NRF sends hardcoded values in NF discovery response

[nitinbhat]

registerIPv4 and port in Configmaps are updated in NFs so that it won't use {{ include "free5gc-pcf.fullname" $ }}-service

NFs use configured IP and port while registering with NRF.

During NF Discovery, NRF doesn't respond with the IP and port (which was used during NF registration) in NF profile but sends default port 80 and tf5gc-free5gc-<NF_NAME>-service

Are NF Profiles hardcoded? Is it not possible to use a custom IP and port in registerIPv4 and port and send the same in NF discovery response?

Also, I see NF discovery is success even before NF is registered with NRF.

For instance,

Check Frame 1923,

Here NRF sends UDR profile to discovery request made by PCF where UDR IP is tf5gc-free5gc-udr-service and port is 80

At this point UDR has not registered with NRF and registration can be seen at frame 2435

Please suggest if there is a way to bypass hardcoded values?

test-NRF.pcap.zip

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.