<p>I'm working through chapter 5.3 of <strong>Kubernetes In Action</strong> by Marko Luska. I'm creating a nodeport service from the <a href="https://github.com/luksa/kubernetes-in-action/blob/master/Chapter05/kubia-svc-nodeport.yaml" rel="nofollow noreferrer">following file</a>:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
  name: kubia-nodeport
spec:
  type: NodePort
  ports:
  - port: 80
    targetPort: 8080
    nodePort: 30123
  selector:
    app: kubia
</code></pre>

<p>It works, and I can hit all the IPs I'm expecting to hit (localhost, cluterIP...) but the external IP is shown as <code>&lt;none&gt;</code>:</p>

<pre class="lang-sh prettyprint-override"><code>$ kubectl get svc 
NAME             TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
kubernetes       ClusterIP   10.96.0.1      &lt;none&gt;        443/TCP        17h
kubia-nodeport   NodePort    10.96.191.43   &lt;none&gt;        80:30123/TCP   12s

$ kubectl get rc --show-labels
NAME    DESIRED   CURRENT   READY   AGE   LABELS
kubia   3         3         3       21h   app=kubia

$ kubectl get po --show-labels
NAME          READY   STATUS    RESTARTS   AGE   LABELS
kubia-fb7h8   1/1     Running   0          17h   app=kubia
kubia-nnkc4   1/1     Running   0          17h   app=kubia
kubia-s88mt   1/1     Running   0          17h   app=kubia
</code></pre>

<p>Minikube should be showing <code>&lt;nodes&gt;</code> as it does in <a href="https://stackoverflow.com/questions/44112150/external-ip-for-kubernetes-shows-nodes-in-minikube">this question</a> and this <a href="https://stackoverflow.com/questions/40767164/expose-port-in-minikube">other question</a>. Why is it not?</p>

mikeLundquist
<p>Probably because this was the case in 2017 and it's not anymore.<br>
The question you're referencing are from 2016 and 2017.</p>

<p>Since then you'll always see <code>&lt;none&gt;</code> unless it's a LoadBalancer. See this <a href="https://github.com/kubernetes/minikube/issues/3966#issuecomment-480097796" rel="nofollow noreferrer">particular comment</a> on github which is from 2019.</p>

<p>Sorry I can't find the PR nor the issue corresponding to that change.</p>
