Description of problem:
In the following document, https://docs.openshift.com/container-platform/3.5/architecture/core_concepts/routes.html#path-based-routes (and similarly 3.6), I would like to ask for clarification to be added with respect to path based routes targeting the path on the filesystem.
Two services, we'll call them 2016 and 2017, both point to a simple hello world application.
Route is created and exposed for the service 2017, "helloworld.mysite.com"
Route is created and exposed for the service 2016, "helloworld.mysite.com/2016"
Both routes have the same hostname, but with the documentation in mind they are taken by most specific to least specific, so if /2016 is targeted then we will be taken to the 2016 service.
Once this occurs, if the 2016 service helloworld application does not have a 2016/ directory, then we'll receive the "Not Found
The requested URL /2016/ was not found on this server."
Error message because the path does not exist. This has led to some confusion that I think could be fixed with a documentation change.
If the path-based route that is set up is expecting the path to be in the file system, adding documentation for this in the aforementioned documents.
If the path-based route that is set up should be taking it to the app source for the service, then instead this should be a bug ticket.
Version-Release number of selected component (if applicable):
Created a PR for the docs: https://github.com/openshift/openshift-docs/pull/7050
The docs LGTM, verified this bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.