I have a vendor product that has services external to Kubernetes. The application calls a web service on a pod and then the pod calls a service external to Kubernetes. When transferring data the external machine calls back on a different port to open a stream. It fails, when tracking this down I found that the service is calling the node and not the pod. The vendor is using the https://akka.io Akka to talk to each other. What the external is doing is not calling back the pod correctly and the node is the destination. Some of the folks involved think it could be an Akka problem, while others believe it could be routing. From what I see looking at Wireshark results is that the callback should be able to contact the pod that called it. But I am not sure on which way to go. Anyone who can guide with some pointers would be helpful.