RFE template

3. What is the nature and description of the request?

   We'd like the ability to define routes in different namespaces that share the
   same hostname but differ on their path. For example: if project A defines
   route for "example.com/app1", then we want project B to be able to define and
   use a route for: "example.com/app2"

4. Why does the customer need this?

   The scenario here is: there's a frontend LB (external to OpenShift) which is
   the entry point to a very limited number of pre-defined esternaly facing
   hostnames (3). The OpenShift cluster exposes many services that are mapped
   using the path components of the URL. These services/apps are developed by
   different teams and belong to different projects/namespaces.

5. How would the customer like to achieve this?

   A suggested implementation would be to add an optional "path_len" parameter
   (default to 0) to the uniqueness check for routes across namespaces, so that
   the unique check is performed using hostname + "path_len" number of path
   segments in the URL.

   For example, if path_len==1 and project A claims "example.com/app1", then
   project B can define "example.com/app2" (unique 1 path segment + hostname)
   but not "example.com/app1/auth". The default value of 0 matches the current
   behaviour: only the hostname would be checked - and in the eample above
   "example.com/app2" would be rejected.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

   See example above

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

   Not that I could find

10. List any affected packages or components.

   controller/routes.