Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certificate List for TCP Services #902

Open
fabiorauber opened this issue Feb 15, 2022 · 2 comments
Open

Certificate List for TCP Services #902

fabiorauber opened this issue Feb 15, 2022 · 2 comments

Comments

@fabiorauber
Copy link

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.

@jcmoraisjr
Copy link
Owner

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 =)

@fabiorauber
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants