# Exposing dashboard, client and ray serve in kubernetes through NodePort

**URL:** <https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497>\
**Category:** Kubernetes\
**Created:** [March 31, 2021, 10:22pm UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497 "2021-03-31T22:22:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![asm582](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/asm582/32/669_2.png) [@asm582](https://discuss.ray.io/u/asm582)\
**Post date:** [March 31, 2021, 10:22pm UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497/1 "2021-03-31T22:22:50Z")

</div>

Hello, We have a Kubernetes environment backed by the load balancer. I am trying to use the above services through NodePort but unable to access them, has anyone used NodePort to access the services instead of clusterIP??

---

<div class="post-metadata">

**Author:** ![eoakes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/eoakes/32/7825_2.png) [@eoakes](https://discuss.ray.io/u/eoakes)\
**Post date:** [April 1, 2021, 2:53pm UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497/2 "2021-04-01T14:53:42Z")

</div>

@Dmitri do you have experience doing this?

---

<div class="post-metadata">

**Author:** ![Dmitri](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/dmitri/32/657_2.png) [@Dmitri](https://discuss.ray.io/u/Dmitri)\
**Post date:** [April 1, 2021, 7:56pm UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497/3 "2021-04-01T19:56:42Z")

</div>

I don’t, but will look into it in the near future.

---

<div class="post-metadata">

**Author:** ![asm582](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/asm582/32/669_2.png) [@asm582](https://discuss.ray.io/u/asm582)\
**Post date:** [April 14, 2021, 2:46pm UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497/4 "2021-04-14T14:46:48Z")

</div>

Hello, can you please share some updates on how can I use NodePort to access kubernetes cluster. I think it’s an important mode to access remote kubernetes cluster where IP’s are scarce resource or in cases where ray clusters are deployed in shared kubernetes environment.

---

<div class="post-metadata">

**Author:** ![Ross\_Morrow](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/ross_morrow/32/1513_2.png) [@Ross\_Morrow](https://discuss.ray.io/u/Ross_Morrow)\
**Post date:** [September 16, 2021, 11:54pm UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497/5 "2021-09-16T23:54:27Z")

</div>

Shouldn’t this be done with a `LoadBalancer` type `Service`? Seems to work for me in GKE (including a `networking.gke.io/load-balancer-type: "Internal"` annotation for VPC only access ) and assigning the resultant LB IP to a DNS record. In EKS you could define annotations in the service to define DNS directly.

---

<div class="post-metadata">

**Author:** ![blublinsky](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@blublinsky](https://discuss.ray.io/u/blublinsky)\
**Post date:** [September 30, 2021, 12:14am UTC](https://discuss.ray.io/t/exposing-dashboard-client-and-ray-serve-in-kubernetes-through-nodeport/1497/6 "2021-09-30T00:14:59Z")

</div>

Assuming that individual cluster nodes have public IPs, Just edit the service replacing type clusterIP to nodeport. [Service | Kubernetes](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport)