News for hackers. Stuff that matters.

A comment on HAProxy 1.8. Parent comment

Re:HAProxy 1.8 by m_mueller on Thursday November 02, 2017 @04:57AM (#15608822)
Thank you. I think dynamic routing would serve our purposes. Am I correct that the map-file as well as the running state needs to be updated separately via commands? I.e. HAProxy syncs between map-file and its runtime state only at setup time, correct?

If so, I have a suggestion: Have a look at what traefik (and before that Hipache) are doing - they use a KVS for the config and sync at runtime, which is quite convenient for dynamic usecases IMO. For the dynamic mapping it would be a better fit than just a file that needs to be manually managed.

[ Parent | on HN ]
Re:HAProxy 1.8 by aiharos on Thursday November 02, 2017 @06:11AM (#15609092)
For ideas on how to make use of the Runtime API to keep servers in a backend up-to-date dynamically, you can also take a look at a HAProxy Kubernetes Ingress Controller implementation that makes use of it here https://github.com/jcmoraisjr/haproxy-ingress#dynamic-scalin...

After 1.8 releases we plan on contributing DNS SRV capability to the controller as well.

[ Parent | on HN ]