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 ar
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 service.
No this is during regular operation.
On Wed, Apr 4, 2018 at 11:39 AM, 'Nicks' via Kubernetes user discussion and
Q&A wrote:
> Did you remove a node from the cluster? Even if a node was in the cluster
> and didn't run any workload, it could still be used to proxy connections
> from the LB and the
What docs have you follow and where it didn't work? So we can better guide
you
On Wednesday, April 4, 2018, Gabriel Sousa
wrote:
> how can i configure a clusterIP ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q&A" group.
>
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 ?
Y
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 ple
I'm not sure what you mean. Can you please elaborate?
On Wednesday, April 4, 2018, Gabriel Sousa
wrote:
> 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 us
Did you remove a node from the cluster? Even if a node was in the cluster
and didn't run any workload, it could still be used to proxy connections
from the LB and the service pod.
On Friday, March 30, 2018 at 7:42:42 AM UTC-7, Tyler Johnson wrote:
>
> Environment: GKE 1.7.12-gke.1
> I believe t
You must have a pre-existing ingress which is pointing to several services
that are type ClusterIP when they should be NodePort. If that ingress is
being used by nginx ingress, make sure you're setting the class
correctly: https://github.com/kubernetes/ingress-nginx#annotation-ingressclass
On
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&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to k
You won't be able to access it through the master IP because it's a
ClusterIP Service rather than a NodePort Service. If you run `kubectl
proxy` it will forward to 127.0.0.1:8001 and you should be able to reach it
at
http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dash
how can i configure a clusterIP ?
--
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
Hello,
Do any of you configured the TLS auth on the newest nginx ingress controller ?
--
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 kube
13 matches
Mail list logo