Gateway API httpRoute sectionName don't seem to do anything unless hostname
is defined
#6306
Open
1 task done
Labels
bug
Something isn't working
Is there an existing issue for this?
Current Behavior
Unless I specify
hostname
when having multiple listeners defined inkind Gateway
, the routing of TLS don't seem to work, and instead I get the following error in the controller.Expected Behavior
Since I'm already defining sectionName in my httpRoute object, Kong shoulden't get any issues with the same SNI.
Example yaml
Steps To Reproduce
And a Gateway
Notice that
hostname: "*.example.com"
is missing from both the listenersThis will give you the following error:
This is even without having a httpRoute defined (which isn't strange from a code point of view).
But if we look at the
httpRoute
object defined above we already useSo why would kong think that it's the same SNI requested for multiple certs?
Kubernetes version
Anything else?
I can imagine this being a pain to solve, and a workaround could be to just document how this works.
I'm wondering how Gateway API think this should work. I haven't looked at this closer, but here you can find the docs: https://gateway-api.sigs.k8s.io/guides/tls/?h=tls#targetrefs-and-tls
The text was updated successfully, but these errors were encountered: