aws
[EKS] [`--service-node-port-range`]: Configurable service-node-port-range
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
I'd like to be able to set --service-node-port-range on kube-apiserver, so I can use a nodeport outside of the default 30000 - 32767.
Which service(s) is this request for? EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? This is, I think, pretty self-explanatory. To give slightly more detail about the motivation, I'm looking at running a hybrid EKS/non-EKS service while doing a migration; it exposes a port below 30000, and it'd be nice to be able to spin up my EKS instances of this service without having to modify the port(s) in use.
Are you currently working around this issue?
I'm experimenting with using hostport instead of nodeport to work around this.
Additional context Anything else we should know?
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
In our context, we need to be exposing a large number of containers to the outside world (at least outside the cluster). This default limits the number that we can do to ~2K containers. (We need to be able to do 10x that...)
Is there a work around to this issue or are EKS clusters limited to ~2K ports?
@maishsk @mikestef9 @toricls is there any planned roadmap for this feature? limiting only ~2k ports restrict many use cases.
Hi @ismith, you were able to workaround this successfully? If you did, could you share please some docs reference to a possible config/solution? Thank you very much
+1 For this feature. We want to move from self managed k8s to EKS and this limitation is creating problem for us.
