Thanks, Tim. That guide was very informative. I was able to get through a few of these steps:
Does the Service have any Endpoints? Yes - verified that three pods were returned Are the Pods working? Verified all three pods are working. Is the kube-proxy working? Yes Is kube-proxy writing iptables rules? This is where I hit an issue. When I run this command in both dev (working) and my new cluster (not working), i see records with "hostname" in them. The guid says " If you do not see these, try restarting kube-proxy with the -V flag set to 4, and then look at the logs again." But I don't know how to do that. Is kube-proxy proxying? Per the guide, I try to do this: `curl 10.59.246.49:80` from a node in the cluster but get "Failed to connect to 10.59.246.49 port 80: Connection refused". So I guess my issue is somewhere between the "is kube-proxy writing uptable rules?" and "is kube-proxy proxying?" I took my YML files that I created my DEV environment (working) and ran them against a brand new cluster in GKE and cannot access the service. I don't know what I did differently the first time I set the cluster up, but I cannot seem recreate it. Any thoughts on how I can further diagnose this? -- 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.
