Joao Morais

Just my 2cents: 10254 has the controller metrics and also some haproxy metrics from the controller's perspective, e.g. the proxy latency and a more accurate idle_pct compatible measure, see some...

Hi, thanks for registering this. This is in fact in the v0.15 roadmap because it's part of the prerequisites to finish the gateway api implementation. Btw nice to see you...

Hi, I'm in the process of building an environment to stress test the controller and the proxy, and your scenario and configuration details are perfect to guide the first tests....

Thanks for the update. Regarding the proxy version you have also the option to build a new image yourself but migrate to v0.13.6 should be safe enough. Regarding possible errors...

Hi, this is an expected behavior due to how the source of data is generated and where they are collected. When a full reload happens - i.e. haproxy cannot apply...

Hey there, nice to see you here as well. Regarding reload strategy I think you don't need to bother with it at all since it only affects how listening sockets...

Hi, thanks for the detailed description. When HAProxy reloads, the listening sockets are copied from the old instance to the new one due to reload-strategy as reusesocket, which is the...

Hi, reusesocket is used to preserve the listening socket open for new connections, it doesn't make any difference for already established connections. You can give native a try, so haproxy...

Hi thanks for the update and sorry about the missing of a feedback. I'm in a hurry since the last weeks to finish a new version and also patching maintenance...

Pods in an unhealthy state (failing readiness) will be removed from the enabled servers of a backend, so health check here is just a guarantee that, if for any reason...