Nodeports are published on all nodes, so any one node going away is not a
problem, per se. but... Nodeports alone require you to use a specific node
IP, which is a problem. Nodeports were designed to be hidden behind
load-balancers or proxies with stable VIPs, which is what it sounds like
you
https://kubernetes.io/docs/setup/independent/high-availability/
"able to contact the NodePort service, from outside the cluster, by
requesting :"
if we Publish a service using nodeport we have the access using
node/master ip , and if that node/master dies ?
we lose the access to the
On Wed, Apr 04, 2018 at 09:33:28AM -0700, Gabriel Sousa wrote:
>
> Now i know what i have to do,
>
> Create a cluster with 3 masters and will use pacemaker/virtual ip and use
> nodeport to Publish services .
Really, can you please elaborate?
>
> can i have only 3 masters without workers ?
Now i know what i have to do,
Create a cluster with 3 masters and will use pacemaker/virtual ip and use
nodeport to Publish services .
can i have only 3 masters without workers ?
On Wednesday, 4 April 2018 17:25:25 UTC+1, Rodrigo Campos wrote:
>
> I'm not sure what you mean. Can you
whats the best solution to Publish services in a independent custom
kubernetes cluster ?
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
