Joao Morais

This doesn't work like this. The annotation is the way to say to controller that your backend is a tcp one, and the presence or absence of the host attribute...

Hi, I've some confidence that this should work without a clusterrole but I didn't explore such configuration yet. I'll leave this issue open so it won't be forgotten.

Nice, thanks! Please let this one open until someone move this hints to the docs or examples.

Yes sure, already tagged as backlog so it won't be forgotten.

Iirc the details of this functionality, the SNI extension has three roles: - choose a proper server certificate to the client; - defines if mTLS should be used and use...

Hi, multi port is already supported, doc [here](http://haproxy-ingress.github.io/docs/configuration/keys/#bind). What do you mean is to bind some ingress to some listening ports - eg listening 8443 and 9443, but only 8443...

Already in the v0.13 roadmap - we'll allow to configure tcp services using ingress resources, this way all L4 compatible backend configurations can be reused - including but not limited...

Yep, `parse-resolv-conf` seems to be a good addition, at least as a config-snippet-like option.

Hi, I'm using a Graylog input to collect HAProxy logs. Note that HAProxy uses UDP. HAProxy process is chrooted before start the event loop, because of that it doesn't have...

I'll leave this open in order to remember to update the examples doc. Thanks for sharing.