Singlehost on OpenShift POC - continuation

[metlos]

With the addition of the Envoy proxy we're still in a research phase of our Singlehost on OpenShift effort.

This issue is meant to work as an umbrella under which we want to arrive at the name of the proxy that we are going to pick for the single host gateway.

To get there, we still need to:

• Develop an Envoy POC Single-host for OpenShift - Envoy testable POCs #17182
• Run perf tests on Envoy POC Run performance tests on Envoy proxy singlehost POC #17243
• Decide whether cookie path rewrites are required
  • Check how cookie path rewrites could be done in HAProxy and Envoy (we know it can be done in nginx and CAN'T be done in Traefik)
• Decide whether location path rewrites are required
  • This can be done in nginx - not sure how to do it in HAProxy, Envoy or Traefik
• Investigate whether the choice between single route for all of Che vs. single route for che and plugins and subdomains for workspaces influences the choice of gateway (it probably doesn't).

[metlos]

We have determined that cookie and location path rewrites are not a crucial feature for us because the user applications will still have to know they are being deployed behind a reverse proxy. For that they will have to make use of the semi-standard X-Forwarded-* headers.