-
Notifications
You must be signed in to change notification settings - Fork 591
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
Generating route fails for wildcard hosts due to invalid name #3311
Comments
It might have worked in the past, as this user here reported a successful route generation of a similar Ingress object: https://discuss.konghq.com/t/workaround-kubernetes-ingress-to-allow-wildcard-hosts/5015 |
Looks like the new combined routes feature is root of this problem. My current solution is to downgrade to version 2.7 (Helm Chart Version 2.13.1), which does not have the |
You can also turn off |
Thanks, is there a straight-forward way to set this via Helm? |
It could be configured by
|
Is there an existing issue for this?
Current Behavior
The following ingress
tries to generate a route object that looks like this
This won't be accepted by the Admin API giving the following error (from the
kong-proxy
logs):Expected Behavior
The route should be generated successfully.
Steps To Reproduce
See above. Pls note, that the service and ingress resource are in the same namespace, which is different from the kong namespace
Kong Ingress Controller version
Kubernetes version
No response
Anything else?
1.23
The text was updated successfully, but these errors were encountered: