Route Admission Policy

[danehans]

What would you like to be added:
The ability to share the same hostname across multiple routes in different namespaces.

Why is this needed:
Administrators and application developers would like to run applications in multiple namespaces with the same domain name. This is for organizations where multiple teams develop microservices exposed on the same hostname.

Allowing hostname claims across namespaces should only be enabled for clusters with trust between namespaces, otherwise a malicious user could take over a hostname. This should therefore be an "opt-in" feature.

[danehans]

xref'ing #49 as this may have ties to spec'ing vhost.

[danehans]

/assign @bowei

cc: @Miciah @ironcladlou

[Miciah]

The main use-case for having multiple routes with the same host name is when the routes have different match rules. For example, one route matches www.example.com/app1 and another route matches www.example.com/app2.

[jpeach]

/kind user-story

[danehans]

Expanding on the example in #60 (comment):

App "foo.example.com" is made up of several app services, each running in a different namespace. For example /login service runs in ns foo-app-login and /content is the main frontend service in ns foo-app-main. Currently, xRoute forwardTo is a "local" object reference so these services must be in the same ns as the xRoute.

[youngnick]

xref #102

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten