<p>minikube version                                                                                                                                                                                        ⏎
minikube version: v0.22.3</p>

<p>I'm trying to setup various pods within a minikube instance. I'm running behind a corporate proxy which may explain some of this behavior.</p>

<p>I start minikube using the following</p>

<p>minikube start --docker-env HTTP_PROXY=<a href="http://corporate-proxy.com:80" rel="nofollow noreferrer">http://corporate-proxy.com:80</a> --docker-env HTTPS_PROXY=<a href="https://corporate-proxy:80" rel="nofollow noreferrer">https://corporate-proxy:80</a> --docker-env NO_PROXY=localhost,127.0.0.0/8,192.0.0.0/8</p>

<p>otherwise it wont work at all. After building some images on docker I created a two services and two pods:</p>

<pre><code>---
apiVersion: v1
kind: Pod
metadata:
  name: app
  labels:
    name: app
spec:
  containers:
    - name: app
      image: image_app
      ports:
        - containerPort: 7777
      volumeMounts:
        - mountPath: /codeage
          name: code-volume
          readOnly: false
      imagePullPolicy: IfNotPresent
      tty: true
  volumes:
   - hostPath:
       path: /codeage
     name: code-volume
---
apiVersion: v1
kind: Pod
metadata:
  name: db
  labels:
    name: db
spec:
  containers:
    - name: db
      image: postgres
      ports:
        - containerPort: 5432
      volumeMounts:
        - mountPath: /var/lib/postgresql
          name: db-data
      imagePullPolicy: IfNotPresent
      tty: true
  volumes:
   - hostPath:
       path: /db-data
     name: db-data
---
apiVersion: v1
kind: Service
metadata:
  name: db
spec:
  type: NodePort
  ports:
  - name: 'db-port'
    port: 5432
    targetPort: 5432
  selector:
    name: db
---
apiVersion: v1
kind: Service
metadata:
  name: app
  labels:
    name: app
spec:
  type: NodePort
  ports:
   - name: apport
     port: 7777
     targetPort: 7777
  selector:
     name: app
---
</code></pre>

<p>I'm unable to ping 'db' from within(ssh) the 'app' pod:</p>

<pre><code>sh-4.2# ping db               
PING db.default.svc.cluster.local (10.0.0.116) 56(84) bytes of data.
From chicago11-rtr-3-v411.us.corporate.com (10.60.172.X) icmp_seq=1 Destination Host Unreachable
^C
</code></pre>

<p>As you can see though nslookup worked and provided the correct clusterIP 10.0.0.116 and hostname 'db.default.svn.cluster.local'</p>

<p>I can ping the node itself. I cannot ping kube-dns...</p>

<p>Anyone have any ideas?</p>

<p>Is there an alternative to using the built in dns service?</p>

<p>we can't ping the service IP address, you can telnet to the port <code>5432</code> defined in the service with service IP.</p>
