<p>I have installed  minikube on my ubuntu 16.04 machine and have started a cluster, with a message </p>

<p><code>"Kubernetes is available at https://192.168.99.100:443"</code></p>

<p>Next, I deployed nginx service with the following command </p>

<p><code>&gt; kubectl.sh run my-nginx --image=nginx --replicas=2 --port=80 --expose</code></p>

<pre><code>&gt; kubectl.sh get  pods -o wide
NAME                        READY     STATUS    RESTARTS   AGE       NODE
my-nginx-2494149703-8jnh4   1/1       Running   0          13m       127.0.0.1
my-nginx-2494149703-q09be   1/1       Running   0          13m       127.0.0.1

&gt; kubectl.sh get  services -o wide
NAME         CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE       SELECTOR
kubernetes   10.0.0.1     &lt;none&gt;        443/TCP   14m       &lt;none&gt;
my-nginx     10.0.0.83    &lt;none&gt;        80/TCP    13m       run=my-nginx

&gt; kubectl.sh get  nodes -o wide
NAME        STATUS    AGE
127.0.0.1   Ready     16m
</code></pre>

<p>Questions:</p>

<p>1) Is node 127.0.0.1 my local development machine? This has got me confused me the most.</p>

<p>2) Is my following understanding correct: The cluster (nodes, kubernetes API server) has internal IP addresses in 10.0.0.x and their corresponding external IP addresses are 192.168.99.x. The 2 pods will then have IPs in the range like 10.0.1.x and 10.0.2.x ?</p>

<p>3) Why is the external IP for the services not there? Not even, for the kubernetes service. Isn't the 192.168.99.43 an external IP here?</p>

<p>4) Most importantly, how do I connect to the nginx service from my laptop?</p>

<blockquote>
  <p>1) Is node 127.0.0.1 my local development machine? This has got me
  confused me the most.</p>
</blockquote>

<p>When a node registers, you provide the IP or name to register with. By default, the node is just registering <code>127.0.0.1</code>. This is referencing your VM running linux, not your host machine. </p>

<blockquote>
  <p>2) Is my following understanding correct: The cluster (nodes,
  kubernetes API server) has internal IP addresses in 10.0.0.x and their
  corresponding external IP addresses are 192.168.99.x. The 2 pods will
  then have IPs in the range like 10.0.1.x and 10.0.2.x ?</p>
</blockquote>

<p>Yup, the 10.0.0.x network is your overlay network. The 192.168.99.x are your "public" addresses which are visible outside of the cluster. </p>

<blockquote>
  <p>3) Why is the external IP for the services not there? Not even, for
  the kubernetes service. Isn't the 192.168.99.43 an external IP here?</p>
</blockquote>

<p>The external IP is typically used to ingress traffic via a specific IP. The kubernetes service is using a clusterIP service type which means it's only visible to the internal cluster. </p>

<blockquote>
  <p>4) Most importantly, how do I connect to the nginx service from my
  laptop?</p>
</blockquote>

<p>The easiest way to view your nginx service is to make it type <code>NodePort</code>, then deploy the service. After that, describe the service to get the port that was assigned (or after you create it will tell you as well). Then hit the ip of your VM and provide the auto assigned NodePort. </p>

<p><code>e.g. http://192.168.99.100:30001
</code></p>
