3 ms·
The confusing part is, how to put a load balancer in front of those deployed servers ?
by revskill 4y ago
The confusing part is, how to put a load balancer in front of those deployed servers ?
- lbotos 4y agoIf your “host servers” are known (say 4 backends) you set up the balancer and point it to the 4 host IPs. If you are dynamically allocating host servers and needing to register them with the LB you should probably consider K8s? This is designed for a “more stable” world: Have some hosts. Have an LB. Deploy containers to those hosts. Avoid superfluous k8s complexity that you don’t need.
- leetrout 4y agoI don't think you need K8S for that. Any decent load balancer (LB) is going to have some concept of origin configuration that weights routing with various algorithms and health checks. You would just update the config in the LB when you bring a new origin online.
- alex_suzuki 4y agoI’m also interested in this setup and have so far only had experience using HAProxy. Any alternatives HN can recommend? (software)
- turtlebits 4y agoLoad balancing isn't part of MRSK - all public clouds offer them, Digitalocean does as well. Or DIY with Haproxy, Nginx, Traefik, etc.
- datadeft 4y agoSorry one of the key part of deploying web applications is not part of the offering.
- cschep 4y agoHe sets up a load balancer in his demo video? Did you watch it?