Hi guys! I am facing a very peculiar issue and was wondering if anyone here had dealt with it before:
I have a pod P1 running on node N1 and a ClusterIP service S1 pointing to P1 I have a pod P2 running on node N1 trying to access service S1 (http://s1.default.svc.cluster.local) - this timesout I have another pod P3 running on node N2 trying to access service S1 (same url) - this works P2 continuously io timeouts, while P3 works fine. As a workaround I have used nodeSelector to make sure P1 is never run with P2 on the same node as a workaround. Now I have a situation where P1 needs to access itself using S1. So pod 1 which has service 1 pointing to it has to access service 1. Already looked at a LOT of github issues and SO and it seems i need to set hairpin mode or install CNI flannel. But it seems that these are only relevant for custom (kubeadm) deployments. I am running on GKE and can't change these...so any ideas? Some info: - Cluster 1.9.4-gke.1 (also with 1.7.12-gke.1) - Node/Master OS is ContainerOS -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
