<p>I have been browsing looking and reading why my external ip is not resolving on Poc I am doing with Minikube .</p>

<p>I am running Minikube on a Ubuntu 16.04 distro.</p>

<p>When i do an http get at <a href="http://192.168.99.100:32431/" rel="nofollow noreferrer">http://192.168.99.100:32431/</a> i get the nginx page.</p>

<p>Is there a why to use external ip with port 80 and not with Minikube ip and the port ?</p>

<blockquote>
  <p>I am running Minikube on a Ubuntu 16.04 distro.</p>
</blockquote>

<p>Minikube is not designed to have an "external ip", it's for simple development-time testing. One will observe it is not even using the <a href="https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/08-bootstrapping-kubernetes-controllers.md#download-and-install-the-kubernetes-controller-binaries" rel="nofollow noreferrer">separate kubernetes binaries/containers</a> that one would expect in a for-real kubernetes deployment</p>

<blockquote>
  <p>Is there a why to use external ip with port 80
  and not with Minikube ip and the port ?</p>
</blockquote>

<p>No to the second half of the question, but if you wish to have the Service listen on port 80 of the minikube VM, then a <a href="https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport" rel="nofollow noreferrer">NodePort Service</a> will very likely do that</p>
