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

Same host in multiple Ingress resources #20

Closed
pleshakov opened this issue Nov 21, 2016 · 3 comments
Closed

Same host in multiple Ingress resources #20

pleshakov opened this issue Nov 21, 2016 · 3 comments
Labels

Comments

@pleshakov
Copy link

What is the correct behavior for Ingress controllers for the case when the same host is defined in multiple Ingress resources incuding resources from different namespaces?

Thx

@eparis
Copy link

eparis commented Nov 21, 2016

OpenShift routes use 'first created'

But that has proven to be very difficult to maintain. A true reservation system with some sort of claims would likely have been a better idea...

@aledbf
Copy link
Member

aledbf commented Nov 21, 2016

in multiple Ingress resources incuding resources from different namespaces?

If the user do not specify a namespace nginx ingress from (contrib) use 'first created'. In case of collisions an event is emitted.

A true reservation system with some sort of claims would likely have been a better idea...

This issue propose exactly that kubernetes/kubernetes#30151

@aledbf
Copy link
Member

aledbf commented Jun 16, 2017

Closing. Please reopen if you have more questions.

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

No branches or pull requests

4 participants