# Kubernetes Custom NodePort Range

**URL:** <https://forums.suse.com/t/kubernetes-custom-nodeport-range/7509>\
**Category:** Rancher 1.x\
**Created:** [October 5, 2017, 10:19pm UTC](https://forums.suse.com/t/kubernetes-custom-nodeport-range/7509 "2017-10-05T22:19:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmachler](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cmachler/32/2915_2.png) [@cmachler](https://forums.suse.com/u/cmachler)\
**Post date:** [October 5, 2017, 10:19pm UTC](https://forums.suse.com/t/kubernetes-custom-nodeport-range/7509/1 "2017-10-05T22:19:12Z")

</div>

Hello,

I am trying to deploy a K8s cluster with a Custom NodePort Range and I am running into some issues.

First I forked the existing K8s template and modifying it by adding the “–service-node-port-range” option under “kubernetes.command.kube-apiserver” in the “docker-compose.yml.tpl” file. I put the fork into a custom catalog, then when I launch it I am getting a “Busy processing [_SERVICE.##_]” error.

Any help on how to accomplish implementing custom nodeport ranges would be greatly appreciated.

-Chris

---

<div class="post-metadata">

**Author:** ![Alireza\_Hanifi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/alireza_hanifi/32/4056_2.png) [@Alireza\_Hanifi](https://forums.suse.com/u/Alireza_Hanifi)\
**Post date:** [May 16, 2018, 9:45am UTC](https://forums.suse.com/t/kubernetes-custom-nodeport-range/7509/2 "2018-05-16T09:45:56Z")

</div>

anybody does not have any solution?