# What is the best way to avoid exposing NodePort

**URL:** <https://discuss.kubernetes.io/t/what-is-the-best-way-to-avoid-exposing-nodeport/15998>\
**Category:** General Discussions\
**Created:** [May 22, 2021, 6:09pm UTC](https://discuss.kubernetes.io/t/what-is-the-best-way-to-avoid-exposing-nodeport/15998 "2021-05-22T18:09:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jyesudian](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/jyesudian/32/7695_2.png) [@jyesudian](https://discuss.kubernetes.io/u/jyesudian)\
**Post date:** [May 22, 2021, 6:09pm UTC](https://discuss.kubernetes.io/t/what-is-the-best-way-to-avoid-exposing-nodeport/15998/1 "2021-05-22T18:09:20Z")

</div>

I am trying to avoid exposing the non standard port in the on premise cluster. I tried ingress controller (nginx) and here too nodeport has to be exposed. Is there any alternates to avoid the same?

### Cluster information:

Kubernetes version: 1.21.1  
Cloud being used: bare-metal  
Installation method: kubeadm  
Host OS: CentOS 7.5  
CNI and version: Calico  
CRI and version: Docker