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
I'm trying to use multiple hostnames for the same TCP port, differentiating them by TLS SNI, each with its own TLS Certificate and backend service. Unfortunately, HAProxy Ingress picks the a single certificate to use for the port, and all other TCP hostnames fail validation by the TLS TCP clients.
What HAProxy Ingress should do or how it should behave differently
If possible, HAProxy Ingress should use a certificate list to present the correct certificate for each hostname, as already works for the HTTPS frontend.
The text was updated successfully, but these errors were encountered:
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 here, I attended to your presentation about Interlegis at 2017 BSA DevOps days =)
That is really nice to hear @jcmoraisjr! BTW, great work on this Ingress Controller, it was exactly what I was looking for. I will see If I can help you with this issue in the coming weeks.
What are you trying to do
I'm trying to use multiple hostnames for the same TCP port, differentiating them by TLS SNI, each with its own TLS Certificate and backend service. Unfortunately, HAProxy Ingress picks the a single certificate to use for the port, and all other TCP hostnames fail validation by the TLS TCP clients.
What HAProxy Ingress should do or how it should behave differently
If possible, HAProxy Ingress should use a certificate list to present the correct certificate for each hostname, as already works for the HTTPS frontend.
The text was updated successfully, but these errors were encountered: