4 ms·
> My only issue has been that there isn't a lot of insight into what is going on with Fabio. There aren't really any configuration options. We have load balanc
by schmichael 7y ago
> My only issue has been that there isn't a lot of insight into what is going on with Fabio. There aren't really any configuration options.
We have load balancing docs for 4 of the most popular load balancers including Fabio: https://www.nomadproject.io/guides/load-balancing/load-balancing.html https://www.nomadproject.io/guides/load-balancing/load-balan... We're monitoring Frank's search for a maintainer but unfortunately don't have the resources to commit to it at the moment. If Fabio becomes abandoned and we're still unable to take over we'll remove it from our docs.
Please feel free to open an issue if you have a specific idea or question. We triage every issue and appreciate user feedback immensely!
- jugg1es 7y agoWow we are really behind. I did not realize that Fabio was in danger of being abandoned. Do you have a recommendation on what we should be doing? I guess we can move to nginx as we have experience with that. Fabio was really nice cuz it just worked. You guys really can't spare the resources to pick up such a necessary part of a container orchestration system? I guess I can see it both ways, where you think that that domain already has very good solutions and you don't want to waste time reinventing the wheel. But then it's much easier for people to pick up your stack and decide to use it when it has load balancing automatically included. Just saying.
- schmichael 7y agoYeah there's definitely lots of internal discussion to see what can be done. Traefik is getting quite popular and is arguably the heir apparent. Nginx and HAProxy also work and are as battle tested as software comes. We may also add a first class notion of ingress load balancing in the future and Envoy would be the natural choice there because we already use it for Nomad's Consul Connect integration.