Feature Request: Add external-k8s-node-ip to service instance Meta

[abckey]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Is your feature request related to a problem? Please describe.

Currently consul-k8s registers service instance into consul with meta including e.g. external-k8s-node-name to indicate which node the service instance is running. However there is no meta to tell what's the node ip.

Feature Description

An extra Meta external-k8s-node-ip could be added for each service instance.

Use Case(s)

external-k8s-node-ip is needed when we want to collect service source IP for traffic originated from service instance(pod) to outside. That information could be used by consul-terraform-sync to dynamically update related firewalls to allow service instance can access certain controlled destinations.

Contributions

I would happy to test this out when the feature is implemented.