Egress SNAT for Pods without matching Service

Is your feature request related to a problem? Please describe. Egress SNAT requires all Pods that should NAT to the Service IP to also be Endpoints of this Service.

Describe the solution you'd like I'm currently implementing a pod watcher which mostly reuses the existing SNAT code in a private fork. Annotating a Pod with kube-vip.io/egress-ipv4-address (or ipv6) labels will trigger kube-vip to configure SNAT rules for "pod ip" -> "ip from annotation". For this to work something else has to ensure that return traffic for the NATed IP is also routed to the k8s node the Pod runs on. This could possibly be done by a k8s LoadBalancer service announcing the IP from the same node, but with a different backend Pod.

Is this something you would be interested in for upstream? If so, I would prepare a PR in the next few days/weeks.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.