service binding to a floating/NAT IP rather than addresses for an interface

[wey-gu]

Background:

If one user would like to access meta/storage from another network, say, nebulagraph in the public cloud, spark cluster on-premise. It's natural to have storaged configured with a public IP provided by NAT/Floating IP of the cloud provider.

Issue:

The storaged won't boot up as it's doing validation based on all addresses of NIC:

https://github.com/vesoft-inc/nebula/blob/2f3259de4673ff3d5c6f2281a6c606375b0afebe/src/common/network/NetworkUtils.cpp#L325-L326

Suggestion:

We should consider allowing addresses to be configured as host ip/service identity but somehow allow internal network routing(to prevent west-east traffic to be routed outside of the OS)?

ref: https://discuss.nebula-graph.com.cn/t/topic/9726/22