You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we're evaluating haproxy as a LB under kubernetes. Our setup is using the haproxy helm chart (https://github.com/haproxytech/helm-charts/tree/main/haproxy) deployed as daemonset, so there will be as many instances as there are nodes.
Since one of our use cases is going to require changing frontends/backends dynamically, we noticed it could be done with the Data Plane API. But we haven't found a way of propagating those changes to all the haproxy instances. As far as we know, a data plane API process has to run on each instance, because it does its magik via the stasts socket, and has to be called individually over each haproxy.cfg file to be able to persist the changes.
Any pointers?
The text was updated successfully, but these errors were encountered:
Currently we're evaluating haproxy as a LB under kubernetes. Our setup is using the haproxy helm chart (https://github.com/haproxytech/helm-charts/tree/main/haproxy) deployed as daemonset, so there will be as many instances as there are nodes.
Since one of our use cases is going to require changing frontends/backends dynamically, we noticed it could be done with the Data Plane API. But we haven't found a way of propagating those changes to all the haproxy instances. As far as we know, a data plane API process has to run on each instance, because it does its magik via the stasts socket, and has to be called individually over each haproxy.cfg file to be able to persist the changes.
Any pointers?
The text was updated successfully, but these errors were encountered: