<p>So I have a service like as follow:</p>

<pre><code>{
 "kind": "Service",
  "apiVersion": "v1",
  "metadata": {
    "name": "monitoring-grafana",
    "namespace": "kube-system",
    "selfLink": "/api/v1/namespaces/kube-system/services/monitoring-grafana",
    "uid": "be0f72b2-c482-11e5-a22c-fa163ebc1085",
    "resourceVersion": "143360",
    "creationTimestamp": "2016-01-26T23:15:51Z",
    "labels": {
      "kubernetes.io/cluster-service": "true",
      "kubernetes.io/name": "monitoring-grafana"
    }
  },
  "spec": {
    "ports": [
      {
        "protocol": "TCP",
        "port": 80,
        "targetPort": 3000,
        "nodePort": 0
      }
    ],
    "selector": {
      "name": "influxGrafana"
    },
    "clusterIP": "192.168.182.76",
    "type": "ClusterIP",
    "sessionAffinity": "None"
  },
  "status": {
    "loadBalancer": {}
  }
</code></pre>

<p>However, whenever I try to access it through the proxy API, it always fails with this response.</p>

<pre><code>http://10.32.10.44:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana/

Error: 'dial tcp 192.168.182.132:3000: getsockopt: no route to host'  
Trying to reach: 'http://192.168.182.132:3000/'
</code></pre>

<p>It happens on all of my services also, not just the one posted.</p>

<p>What could be going wrong? Is something not installed?</p>

<p>Looking at the error you posted it seems like the traffic can not be routed from your <strong>master</strong> to the Docker subnet of your <strong>node</strong>. The easiest way to validate this is to open a shell on your master and perform a request on your <em>podIP:daemonPort</em>: <code>curl -I http://192.168.182.132:3000</code></p>

<p>Each node in your cluster should be able to communicate with every other node, and every Docker subnet should be routable. For most deployments you will need to setup an extra network fabric to make this happen, like flannel or Weave.</p>

<p>Take a look at <a href="http://kubernetes.io/docs/getting-started-guides/scratch/#network" rel="nofollow">Getting started from Scratch >> Network</a></p>

<hr>

<p>Something else is funny. The cluster IP used by your service (192.168.182.76) and the pod IP of the endpoint (192.168.182.132) <em>seem</em> to be in the same subnet. However you need 3 different subnets:</p>

<ul>
<li>one for the hosts</li>
<li>one for the Docker bridges (<code>--bip</code> flag of Docker)</li>
<li>one for the service (<code>--service-cluster-ip-range=</code> of the API server)</li>
</ul>
