<p>I have a service exposed of type=LoadBalancer and when I do a</p>
<p><code>kubectl describe services servicename</code>,</p>
<p>I get this output :</p>
<pre><code>Name:           ser1
Namespace:      default
Labels:         app=online1
Selector:       app=online1
Type:           LoadBalancer
IP:         10.0.0.32
External IPs:       192.168.99.100
Port:           &lt;unset&gt; 8080/TCP
NodePort:       &lt;unset&gt; 30545/TCP
Endpoints:      172.17.0.10:8080,172.17.0.11:8080,172.17.0.8:8080 + 1 more...
Session Affinity:   None
</code></pre>
<p>Can someone please guide on the following doubts :</p>
<p>1.) I can't understand what <code>&lt;unset&gt;</code> means in Port and NodePort. Also, how does it affect my service?</p>
<p>2.) When I want to hit a service, I should hit the service using <code>&lt;external-ip:NodePort&gt;</code> right? Then what's the use of Port?</p>

Dreams
<p><strong>Port unset</strong> means: You didn't specify a name in service creation.</p>

<p>Service Yaml excerpt (note <code>name: grpc</code>):</p>

<pre><code>spec:
  ports:
  - port: 26257
    targetPort: 26257
    name: grpc
  type: NodePort
</code></pre>

<p><code>kubectl describe services servicename</code> output excerpt:</p>

<pre><code>Type:                   NodePort
IP:                     10.101.87.248
Port:                   grpc    26257/TCP
NodePort:               grpc    31045/TCP
Endpoints:              10.20.12.71:26257,10.20.12.73:26257,10.20.8.81:26257
</code></pre>

<p><strong>Port</strong> is definition of container ports that service will send the traffic on (Actual Endpoint).</p>
