<p>I make configuration that my service is builded on 8080 port.</p>

<p>My docker image is also on 8080.</p>

<p>I put my <strong>ReplicaSet</strong> with configuration like this</p>

<pre><code>apiVersion: apps/v1
kind: ReplicaSet
metadata:
 name: my-app-backend-rs
      spec:
       containers:
       - name: my-app-backend
         image: go-my-app-backend
         ports:
         - containerPort: 8080
         imagePullPolicy: Never
</code></pre>

<p>And finally I create service of type <strong>NodePort</strong> also on port 8080 with configuration like below:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
 labels:
  app: my-app-backend-rs
 name: my-app-backend-svc-nodeport
spec:
 type: NodePort
 ports:
 - port: 8080
   protocol: TCP
   targetPort: 8080
 selector:
  app: my-app-backend
</code></pre>

<p>And after I put describe on NodePort I see that I should hit (e.g. curl <a href="http://127.0.0.1:31859/" rel="nofollow noreferrer">http://127.0.0.1:31859/</a>) to my app on address <code>http://127.0.0.1:31859</code>, but I have no response.</p>

<pre><code>Type:                     NodePort
IP:                       10.110.250.176
Port:                     &lt;unset&gt;  8080/TCP
TargetPort:               8080/TCP
NodePort:                 &lt;unset&gt;  31859/TCP
Endpoints:                172.17.0.6:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   &lt;none&gt;
</code></pre>

<p>What am I not understanding and what am I doing wrong? Can anyone explain me that?</p>

Adriano
<p>From your output,i'm seeing below endpoint is created.So it seems one pod is ready to serve for this nodeport service.So label is not an issue now.</p>

<pre><code>Endpoints:                172.17.0.6:8080
</code></pre>

<p>First ensure you are able to access the app by running curl <a href="http://podhostname:8080" rel="nofollow noreferrer">http://podhostname:8080</a> command, once you are login into the pod using kubectl exec -it podname sh(if curl is installed on image which running in that pod container).If not run curl ambassador container pods as sidecar and from that pod try to access the http://&lt;>:8080 and ensure it is working.</p>

<p>Remember you can't access the nodeport service as localhost since it will be pointing to your master node,if you are running this command from master node.
You have to access this service by below methods.</p>

<pre><code>&lt;CLUSTERIP:PORT&gt;---In you case:10.110.250.176:80
                      &lt;1st node's IP&gt;:31859
                      &lt;2nd node's IP&gt;:31859
</code></pre>
