-
Notifications
You must be signed in to change notification settings - Fork 272
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
https route does not work as expected #1071
Comments
Adding "tls" in the gateway allows to generate the expected "_front_https_host__prefix.map":
The "tls" configuration in gateway listener should be enough, but I had to add the command-line parameter "default-ssl-certificate" to make the frontend tls use-case work. Maybe something to improve at this level to make the configuration self-contained in one place. |
Hi, in fact Gateway API is not fully implemented on our side, so we're not properly updating status (so you don't know what's going wrong). Regarding the HTTPS configuration, we already have the info in place:
Source: doc Regarding the self-contained configuration, if I understood you correctly, a gateway resource has the ability to configure just a single hostname, and the certificate for that single hostname. If you check the hostname certificate:
you can see that haproxy uses the one I configured in the listener. But if however you need to use the same one as default if a hostname doesn't match or is not provided, you should configure it via |
This issue got stale and will be closed in 7 days. |
Description of the problem
When I define a simple Kubernetes Gateway, HTTPRoute, Service and EndpointSlice for http requests, the haproxy http frontend is correctly generated and the requests work fine. However, if I replace http with https the https frontend is wrongly generated and the requests get 404.
Expected behavior
https frontend is correctly generated (see below expected frontend).
https request "curl -v https://example.api.net" should return 200 OK.
Steps to reproduce the problem
Environment information
HAProxy Ingress version:
v0.14.5
Expected https frontend:
Generated https frontend:
Expected "_front_https_host__prefix.map":
The problem is that "_front_https_host__prefix.map" was not generated at all, which causes the 404.
Is there any workaround or fix to resolve this issue?
Thanks
The text was updated successfully, but these errors were encountered: