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
Allow wildcard routing in host #960
Comments
I'm interested in such a feature as well 🤞 |
@M00nF1sh Is there any chance this will be picked up in next release you are planning? |
@ashish4github i'm taking a look at this, and i'm actually surprised if this it not supported already... |
@ashish4github just tested that this is already supported. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are implementing a SaaS based solution and need service calls for all subdomains to be routed to a same service. For example, both below service calls from browser should be touted to service.
tenanta.example.com/service1,
tenantb.example.com/ service1
How can I achieve this with single ingress resource? We tried using the host entry as *.example.com but that did not work.
As per the https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/20190125-ingress-api-group.md this feature is supported in most of teh ingress controller and widely used; and thus proposed to be added to spec.
Is there any plan to support this for alb-ingress controller?
The text was updated successfully, but these errors were encountered: