<p>I have set up a Kubernetes cluster. The cluster contains, among other things, a cluster and deployment surfacing an API webservice (based on the <a href="https://github.com/ResidentMario/subway-explorer-gmaps-proxy" rel="nofollow noreferrer"><code>subway-explorer-gmaps-proxy</code></a> container).</p>

<p>I've deployed the service externally, using the <code>LoadBalancer</code> service type (this is on GCP):</p>

<pre><code>$kubectl get svc subway-explorer-gmaps-proxy-service
NAME                                  TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)          AGE
subway-explorer-gmaps-proxy-service   LoadBalancer   10.35.252.232   35.224.78.225   9000:31396/TCP   19h
</code></pre>

<p>My understanding (and correct me if I'm wrong!) is that this service should now be queryable outside of the cluster, by visiting <code>http://35.224.78.225</code> in the browser.</p>

<p>When running the Docker container locally, I can verify things are working correctly by navigating to the following URL:</p>

<pre><code>http://localhost:49161/starting_x=-73.954527&amp;starting_y=40.587243&amp;ending_x=-73.977756&amp;ending_y=40.687163
</code></pre>

<p>Looking at the <code>kubectl get</code> output, I expect visiting the following URL in the browser will serve me the content I'm looking for:</p>

<pre><code>http://35.224.78.225:31396/starting_x=-73.954527&amp;starting_y=40.587243&amp;ending_x=-73.977756&amp;ending_y=40.687163
</code></pre>

<p>But when I visit this URL, nothing gets served.</p>

<p>I suspect there is a non-fatal error in the deployment configuration. What is an effective way of debugging this effective way of debugging this problem? Are there access logs or a <code>stdout</code> stream somewhere I can check to see what's wrong?</p>

<p>You can try running through the official docs on debugging services: <a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/</a></p>

<p>Beyond that, have you confirmed you're querying the load balancer on the right port? While I don't deploy on GCP, when launching a load balancer for a kubernetes service on AWS it'll accept traffic on port 80/443 and forward it to the NodePort of the service, which I'm guessing is 31396 for your case. What are the ports listed in <code>kubectl get svc subway-explorer-gmaps-proxy-service -o yaml</code>? </p>
