Annika Wickert

This is indeed interesting. So this is all we do to the response header `http-response set-header X-Backend Kubernetes`

@capflam it existed on 3.0.4 as well, we test 3.0.5 next but we are quite busy atm with Universe upcoming :D.

This patch is btw applied https://github.com/haproxy/haproxy/issues/2611

@capflam that patch is already applied, as I reported the bug #2611 and this seems to be a new bug even with the patch applied.

Hehe, happens thanks! Build is running, will report back :).

I didn't observe any crash so far, I try to roll it to a few more servers which showed the behaviour more often.

I am wondering if this is also the same issue we see here https://github.com/haproxy/haproxy/issues/2696

I investigated a bit further, so it seems the iptables rules generated are only using the table "local" to get the list of local IPs: ` 324 28112 DOCKER all...

Our experimental firmware (http://firmware.ffmuc.net/experimental/) now applies all your patches. It's looking good so far. And as most people in our chat (https://chat.ffmuc.net) confirmed they are fine to break the old...