Pod cannot call it's own service about dcos-kubernetes-quickstart HOT 6 CLOSED

Thank you. The workaround works, and with it I'm able to deploy and succesfully run Flink 1.5 on kubernetes on DCOS.

from dcos-kubernetes-quickstart.

Good news is that I was able to replicate it. Bad news is that a few minutes later as soon as I started doing a network capture the issue vanished and I was able to call the service from the pod it's pointing to.

So... it seems to be an issue with the overlay. I'll follow up with the networking team and provide more details as soon as possible.

from dcos-kubernetes-quickstart.

fixed

from dcos-kubernetes-quickstart.

Thanks for reporting. We will be looking into it soon.

from dcos-kubernetes-quickstart.

So it's not an overlay issue and it's related to how we are not setting the hairpin mode correctly.

This ticket in kubernetes provided the clue kubernetes/kubernetes#13375

Has a workaround until we release a proper fix I suggest setting it manually. For example like this:

$ dcos task exec -ti kube-node-N-kubelet bash
...
$ for intf in /sys/devices/virtual/net/m-dcos/brif/*; do echo 1 > ${intf}/hairpin_mode; done

from dcos-kubernetes-quickstart.

@rsltrifork We enabled hairpin mode by default in the new release. Can you test it and then close close the ticket?

from dcos-kubernetes-quickstart.