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?
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 wrote:
>
> Hi Tim,
>
> Thanks for your reply. I'll explain our uses case below.
>
> Our uses case is that we provide a service
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
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 wrote:
>
> For our use-case, we need to access a lot of services via
For our use-case, we need to access a lot of services via NodePort. By
default, the NodePort range is 3-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
