I am running kubernetes single node on coreos.

I have created a pod running a python application and exposing an http endpoint.

I have created a kubernetes service that exposes the HTTP endpoint. I have exposed this service using NodePort and can call it successfully from outside the cluster.

What I am then trying is to call the HTTP service from a docker container. To test I am just using the same running container and using curl.

I can docker exec into the docker container running my service. nslookup for 'my-service' resolves to an IP address. So I am happy that DNS service registration is working correctly. (I have also checked that the ENV variables for the service exist - and they do and are the same as the value returned from nslookup)

However, if I then try:

curl http://my-service:9042/status

It just hangs with no response. (Port 9042 is the correct port and status is a valid resource)

I'm assuming that I'm missing something really obvious. Any suggestions warmly received.

Update:

The response of curl -v is:

root@lake-cluster-manager:/# curl -v http://lake-service:9042/status
* Hostname was NOT found in DNS cache
*   Trying 10.3.0.128...

The output from nslookup is:

root@lake-cluster-manager:/# nslookup lake-service   
Server:     10.3.0.10
Address:    10.3.0.10#53

Name:   lake-service.default.svc.cluster.local
Address: 10.3.0.128