Joao Morais

#274

Hi thanks for bringing this missing feature back to our attention. This is a missing implementation since the v0.8 refactor as stated here: https://github.com/jcmoraisjr/haproxy-ingress/blob/b5853e1419467cee9873f94b5f4aa1748789f382/pkg/converters/utils/services.go#L117-L122 There are some parts of the...

Fixed in `v0.14.0-beta.2` and merged to v0.13 as well, so next v0.13 will have this same fix. Closing.

Hi, thanks for the detailed report and sorry about the long delay. Yes it's pretty clear and your request makes sense. I'm not sure you can dynamically configure it, anyway...

Hi, v0.9+ addresses this issue on backends secured by tls certificates due to security reasons - a 421 http response is sent to the client whenever sni and host header...

Hi, this is a probably somewhat simple and low/mid impact implementation. I'm also interested in it and maybe it can fit in the v0.15 release. Regarding releases we've v0.15 planned...

No problem, take your time, thanks! I'll let you know about any progress from my side updating this issue.

@arun11299 just to let you know that I'll need to bring the controller-runtime migration to v0.15 and this will completely change how the current listers and informers work. I'll update...

Hi this is currently unsupported, unfortunately, but it's already a v0.15 roadmap. You can circumvent this configuring the bind port to an unused one, eg `https-port: "9443"` or something like...

Great, just labeling this as an enhancement in order to properly update the `examples`. Tks!