Sound like a potential solution. Thank Tim, we will try this approach to see if it works for our case.
On Monday, 17 September 2018 11:48:09 UTC+8, Tim Hockin wrote: > > Hmm, this is a bit of a stretch for NodePorts. Why not use a HostPort > and update DNS dynamically if/when their VM updates? > On Sun, Sep 16, 2018 at 6:30 PM Phạm Huy Hoàng <huyho...@gmail.com > <javascript:>> wrote: > > > > Hi Tim, > > > > Thanks for your reply. I'll explain our uses case below. > > > > Our uses case is that we provide a service as a Linux VM so that user > can SSH and VNC into that VM. > > Each VM is run as a stateful set in GKE cluster. > > > > For each user, we need to provide expose 2 ports via a service (1 for > VNC and one for SSH). > > We do not use LoadBalancer service, because the price of 1 forwarding > rule is ~4-6 USD, that will increase our cost per user to 4-6USD/month. > > Therefore, we use nodePort service. Because the port range is > 30000-32767, it means 1 cluster can only serve about ~1400 users. > Currently, our user base is ~500 so it might not be a problem, but it might > be in the future. > > > > My naive solution is to increase the port range so a cluster might be > able to serve more users. If the number of users becomes big enough, maybe > we can consider creating another cluster. > > > > Thanks. > > > > On Friday, 14 September 2018 23:46:24 UTC+8, Tim Hockin wrote: > >> > >> We do not expose that as a parameter today. We can discuss the > >> options here, but there's not short answer. Can you talk about what > >> you're doing to need so many node ports? > >> On Fri, Sep 14, 2018 at 8:27 AM Phạm Huy Hoàng <huyho...@gmail.com> > wrote: > >> > > >> > For our use-case, we need to access a lot of services via NodePort. > By default, the NodePort range is 30000-32767. With kubeadm, I can set the > port range via --service-node-port-range flag. > >> > > >> > We are using Google Kubernetes Engine (GKE) cluster. How can I set > the port range for a GKE cluster? > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > Groups "Kubernetes user discussion and Q&A" group. > >> > To unsubscribe from this group and stop receiving emails from it, > send an email to kubernetes-use...@googlegroups.com. > >> > To post to this group, send email to kubernet...@googlegroups.com. > >> > Visit this group at https://groups.google.com/group/kubernetes-users. > > >> > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google > Groups "Kubernetes user discussion and Q&A" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to kubernetes-use...@googlegroups.com <javascript:>. > > To post to this group, send email to kubernet...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/kubernetes-users. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
