title: Selenium Chrome Node doesn't resolve urls on kubernetes with Scalatest
body: <p>I'm using Scalatest and Selenium for testing. The Selenium Hub and the Chrome node are running on 2 Kubernetes Pods.<br>
  I have the webservice I need to test on another pod. It has an internal address <a href="http://myui.dev/" rel="nofollow noreferrer">http://myui.dev/</a>. It's not accessible from outside.<br>
  The test continue to fail. When the webdriver is trying to reaching the internal url the page is getting is the ERR_CONNECTION_TIMED_OUT page on Chrome.</p>
  
  <p>I tried to:  </p>
  
  <ul>
  <li>connect from scalatest to another url (www.google.co.uk) and it
  <strong>worked</strong>.  </li>
  <li>I've tried to access the the selenium hub container and I can curl either <strong>google</strong> or my <strong>internal</strong> url. </li>
  <li>I've accessed the pod with the
  chrome node and curl the url. It <strong>worked</strong> as well.</li>
  </ul>
  
  <p>So, my best guess it's that for some reason it's not taking or overriding the /etc/resolv.conf inside the container.</p>
  
  <p>Any idea how to fix this?</p>
  
  <p>Some configuration that could be helpful:</p>
  
  <ul>
  <li>scalatest version: 3.0.5 </li>
  <li>selenium-java version: 3.12.0 </li>
  <li>Selenium Hub image: selenium/hub:latest     </li>
  <li>Selenium Chrome node image:
  selenium/node-chrome:latest</li>
  </ul>
  
  <p>The pod configuration:</p>
  
  <pre><code>apiVersion: extensions/v1beta1
  kind: Deployment
  metadata:
    labels:
       service: selenium-chrome
    name: selenium-chrome
  spec:
    replicas: 1
    strategy: {}
    template:
      metadata:
        labels:
          service: selenium-chrome
      spec:
        containers:
        - env:
          - name: HUB_HOST
            value: selenium-hub
          - name: NODE_MAX_INSTANCES
            value: "10"
          - name: NODE_MAX_SESSION
            value: "10"                
          image: selenium/node-chrome:latest
          name: selenium-chrome
          volumeMounts:
              - mountPath: /dev/shm
                name: extended-mem
          imagePullPolicy: Always
          resources: {}
        restartPolicy: Always
        volumes:
          # extended memory for the browser
          - name: extended-mem
            hostPath:
              path: /dev/shm
  status: {}
  </code></pre>
  
  <p><strong>UPDATE [25/06/2018]:</strong><br>
  I've figure it out. Apparently wasn't a dns problem. As Matthew suggested it's not a DNS problem. Indeed when I run:    </p>
  
  <pre><code>kubectl run selenium-hub --image selenium/hub --port 4444
  kubectl expose deployment selenium-hub --type=NodePort
  kubectl run selenium-node-chrome --image selenium/node-chrome --env="HUB_PORT_4444_TCP_ADDR=selenium-hub" --env="HUB_PORT_4444_TCP_PORT=4444"
  </code></pre>
  
  <p>it works.</p>