# Nodeport type service not creating remote endpoint

**URL:** <https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112>\
**Category:** General Discussions\
**Created:** [August 28, 2022, 1:09pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112 "2022-08-28T13:09:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![smtp\_server](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/smtp_server/32/10713_2.png) [@smtp\_server](https://discuss.kubernetes.io/u/smtp_server)\
**Post date:** [August 28, 2022, 1:09pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/1 "2022-08-28T13:09:47Z")

</div>

I’m trying to create a service from minikube with virtualbox as hypervisor driver. It is able to create endpoints for matching pods with cluster ip address. But endpoint for outside the cluster is not being made even though it’s nodeport type service. In VM hosting this minikube cluster, I checked all sockets but the one to access service from outside the cluster is not really being created.

```auto
apiVersion: v1
kind: Service
metadata:
  name: sample-service
spec:
  type: NodePort
  selector:
      app: sample-app
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080
    nodePort: 31000  

```

---

<div class="post-metadata">

**Author:** ![Theog75](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/theog75/32/9241_2.png) [@Theog75](https://discuss.kubernetes.io/u/Theog75)\
**Post date:** [August 28, 2022, 2:15pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/2 "2022-08-28T14:15:55Z")

</div>

1. check that the selector ` app:sample-app` is one of the pods label
2. can you please send the output of:

```auto
kubectl get ep sample-service -n <namespace>

```

?

---

<div class="post-metadata">

**Author:** ![smtp\_server](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/smtp_server/32/10713_2.png) [@smtp\_server](https://discuss.kubernetes.io/u/smtp_server)\
**Post date:** [August 28, 2022, 2:32pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/3 "2022-08-28T14:32:00Z")

</div>

1. Yea. That’s not a problem.

2. 

Name: sample-service Namespace: default Labels: Annotations: Subsets: Addresses: 172.17.0.10,172.17.0.11,172.17.0.4,172.17.0.5,172.17.0.7,172.17.0.8,172.17.0.9 NotReadyAddresses: Ports: Name Port Protocol ---- ---- -------- 8080 TCP Events:

---

<div class="post-metadata">

**Author:** ![Theog75](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/theog75/32/9241_2.png) [@Theog75](https://discuss.kubernetes.io/u/Theog75)\
**Post date:** [August 28, 2022, 3:19pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/4 "2022-08-28T15:19:59Z")

</div>

what is the machine’s IP address? is it one of the IPs you listed?

---

<div class="post-metadata">

**Author:** ![smtp\_server](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/smtp_server/32/10713_2.png) [@smtp\_server](https://discuss.kubernetes.io/u/smtp_server)\
**Post date:** [August 28, 2022, 3:23pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/5 "2022-08-28T15:23:05Z")

</div>

No, all of them are cluster IPs only. VM’s eth IP address is 192.168.59.102

---

<div class="post-metadata">

**Author:** ![thockin](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/thockin/32/2457_2.png) [@thockin](https://discuss.kubernetes.io/u/thockin)\
**Post date:** [August 28, 2022, 3:34pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/6 "2022-08-28T15:34:27Z")

</div>

The VM NIC is not considered an endpoint the way pods are. The selector only selects pods.

---

<div class="post-metadata">

**Author:** ![smtp\_server](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/smtp_server/32/10713_2.png) [@smtp\_server](https://discuss.kubernetes.io/u/smtp_server)\
**Post date:** [August 28, 2022, 3:41pm UTC](https://discuss.kubernetes.io/t/nodeport-type-service-not-creating-remote-endpoint/21112/7 "2022-08-28T15:41:57Z")

</div>

That’s right. Pods would be final endpoints but by endpoint, I meant socket on node which would let one access service from outside cluster as expected from nodeport type service. So these logical cluster specific endpoints are being made but one on node is not.  
When I try to curl nodeport from host machine it says ‘site refused to connect’ and actually socket is not being created on node.