Hi Rodrigo,
I could create the NodePort service for the ingress controller, but that still
requires a an external component (something outside kubernetes) that is
relaying/redirecting/load_ballancing traffic from the border of my network to the
kubernetes nodes on the port provided by the nodePort. (www.my-org-name.org:80
--> one-of-kubernetes-nodes:NodePort).
Kind regards,
Laszlo
On 25.09.2017 16:18, Rodrigo Campos wrote:
Can't you create a service type node Port and then route to all the nodes?
Sorry, never used ingress, but don't see why this won't work.
On Monday, September 25, 2017, Budai Laszlo <laszlo.bu...@gmail.com
<mailto:laszlo.bu...@gmail.com>> wrote:
Hi Tim,
Thank you for your answer.
This practically mean that we have to pay attention where the ingress
controller is scheduled and how it is implemented (in terms of HA), otherwise
we may end up running the ingress controller on a node where there is no
traffic coming from outside ...
Kind regards,
Laszlo
On 25.09.2017 15:29, 'Tim Hockin' via Kubernetes user discussion and Q&A
wrote:
You have to arrange that traffic delivery. Kubernetes doesn't
intrinsically know your network, unless you are on one of the major clouds.
A common answer is to DNS-roundrobin the nodes' public IPs, or to
configure your L3 infrastructure to VIP to your nodes.
On Sep 25, 2017 1:41 AM, <laszlo.bu...@gmail.com
<mailto:laszlo.bu...@gmail.com>> wrote:
Dear all,
I've read the documentation about ingress, and ingress controller
(https://kubernetes.io/docs/concepts/services-networking/ingress/
<https://kubernetes.io/docs/concepts/services-networking/ingress/>
<https://kubernetes.io/docs/concepts/services-networking/ingress/
<https://kubernetes.io/docs/concepts/services-networking/ingress/>>,
https://github.com/kubernetes/ingress/tree/master/controllers
<https://github.com/kubernetes/ingress/tree/master/controllers>
<https://github.com/kubernetes/ingress/tree/master/controllers
<https://github.com/kubernetes/ingress/tree/master/controllers>>). There is a statement that says: "An Ingress
Controller is a daemon, deployed as a Kubernetes Pod". My question is how the traffic for our application is routed to
the ingress controller Pod?
For example: an organization has an internal k8s cluster, and
wants to use the nginx ingress controller. When the controller is deployed as a
Pod it will still run on the internal cluster. Then we create the ingress
resource with a rule like this:
- host: www.my-org-name.org <http://www.my-org-name.org>
<http://www.my-org-name.org>
http:
paths:
- backend:
serviceName: webapp
servicePort: 12345
where the name www.my-org-name.org <http://www.my-org-name.org>
<http://www.my-org-name.org> is resolved to one of the public IPs the organization
has. So how do the traffic coming from outside will reach the 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 kubernetes-users+unsubscr...@googlegroups.com
<mailto:kubernetes-users%2bunsubscr...@googlegroups.com>.
To post to this group, send email to kubernetes-users@googlegroups.com
<mailto:kubernetes-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/kubernetes-users
<https://groups.google.com/group/kubernetes-users>
<https://groups.google.com/group/kubernetes-users
<https://groups.google.com/group/kubernetes-users>>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout> <https://groups.google.com/d/optout
<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
<mailto:kubernetes-users+unsubscr...@googlegroups.com>.
To post to this group, send email to kubernetes-users@googlegroups.com
<mailto:kubernetes-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/kubernetes-users
<https://groups.google.com/group/kubernetes-users>.
For more options, visit https://groups.google.com/d/optout
<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
<https://groups.google.com/group/kubernetes-users>.
For more options, visit https://groups.google.com/d/optout
<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
<mailto:kubernetes-users+unsubscr...@googlegroups.com>.
To post to this group, send email to kubernetes-users@googlegroups.com
<mailto: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.
--
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.
