Using a single host with multiple ingresses on OpenShift - Part 2 - native ingress support
Consider the following legacy application migration scenario that has two macro components. The typical pre-containerization application deployment scenario may have had these hosted on VM's with a reverse proxy handling requests to a single logical host endpoint. Both macro components present REST interfaces and are expecting to see the most simple request URI possible. One of the components can be considered the primary monolithic application and the other is like a plug-in or supporting module.
The reverse proxy design took almost all of the traffic, e.g.
/ and sent that to the primary application. For the supporting module, only requests to
/sub-module/(.*) the reverse proxy does a rewrite of the path in the URI to only contain the matched subpath and adds a request header so that the fully qualified paths can be built into responses. In this example, for an incoming request like
/sub-module/foo/bar the re