4 ms·
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 GitL
by mdaniel 6y ago
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)
- renke1 6y agoHow do you typically access your K8S cluster when it's not fronted by a LB and it has multiple nodes?
- withinboredom 6y agoYou 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.
- champtar 6y agoMetalLB in L2 or BGP mode
- tijsvd 6y agoAt 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.