Comparison of Kubernetes Ingress Controllers

Re:Comparison of Kubernetes Ingress Controllers by mdaniel on Thursday October 22, 2020 @11:19AM (#24858935)

In addition to the great sibling comment, another reason is typically cost: if I had to provision a new cloud load balancer for every review environment in GitLab, that'd be quite pricy (and much, much slower to deploy)

[ Parent | on HN ]

Re:Comparison of Kubernetes Ingress Controllers by renke1 on Thursday October 22, 2020 @11:24AM (#24858999)

How do you typically access your K8S cluster when it's not fronted by a LB and it has multiple nodes?

[ Parent | on HN ]

Re:Comparison of Kubernetes Ingress Controllers by tijsvd on Thursday October 22, 2020 @02:36PM (#24861610)

At least in AWS, it will by default instantiate an application LB for every ingress (so at least one per namespace).

With an internal ingress controller, one can combine all ingresses into e.g. a single nginx service. That service can then be fronted by one single network LB for the whole cluster.

[ Parent | on HN ]

Re:Comparison of Kubernetes Ingress Controllers by withinboredom on Thursday October 22, 2020 @12:59PM (#24860229)

You can assign multiple ips to the same dns entry. It’s not quite as flexible as a load balancer, but sometimes that’s all you need.

[ Parent | on HN ]

Re:Comparison of Kubernetes Ingress Controllers by champtar on Thursday October 22, 2020 @01:40PM (#24860761)

MetalLB in L2 or BGP mode

[ Parent | on HN ]