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

Allow wildcard routing in host #960

Closed
ashish4github opened this issue Jun 24, 2019 · 4 comments
Closed

Allow wildcard routing in host #960

ashish4github opened this issue Jun 24, 2019 · 4 comments

Comments

@ashish4github
Copy link

ashish4github commented Jun 24, 2019

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?

@tareksamni
Copy link

I'm interested in such a feature as well 🤞

@ashish4github
Copy link
Author

@M00nF1sh Is there any chance this will be picked up in next release you are planning?

@M00nF1sh
Copy link
Collaborator

M00nF1sh commented Jul 12, 2019

@ashish4github i'm taking a look at this, and i'm actually surprised if this it not supported already...

@M00nF1sh
Copy link
Collaborator

M00nF1sh commented Jul 12, 2019

@ashish4github just tested that this is already supported.
With one tip, u should quote the host like "tenant*.example.com" :D, if you use * in yaml, you need to quote it 😄

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

No branches or pull requests

3 participants