# Is the nodePort number stable after it is created?

**URL:** <https://discuss.kubernetes.io/t/is-the-nodeport-number-stable-after-it-is-created/11232>\
**Category:** General Discussions\
**Created:** [June 2, 2020, 11:04pm UTC](https://discuss.kubernetes.io/t/is-the-nodeport-number-stable-after-it-is-created/11232 "2020-06-02T23:04:02Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [June 4, 2020, 5:33pm UTC](https://discuss.kubernetes.io/t/is-the-nodeport-number-stable-after-it-is-created/11232/6 "2020-06-04T17:33:52Z")

</div>

The NodePort is allocated synchronously today, though I don’t think I  
would advise to depend on that. We’re looking to add new APIs that  
serve the same purpose but are factored better (called Gateway) and  
there’s some value to allowing async allocation (more like  
load-balancer IPs). Service will almost certainly not BREAK the  
current assumption, but I don’t want to guarantee that Gateway will  
retain it.

---

_[View the full topic](https://discuss.kubernetes.io/t/is-the-nodeport-number-stable-after-it-is-created/11232)._