beyondcorp

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

I need to do a collateral call to google APIs from my backend to get additional information about the user (full name, profile picture, team, ...). For that, I need to have the access token. Unfortunately, now I only have access to the user's email.

A solution could be to return the access token in the header key X-Forwarded-AccessToken but I think we will have to manage when the access token

Need a modern, nice looking design for http status code page

• one status page that can be used for different kinds of status codes (400,401,403,404,500)
• css, images and everything emdedded into one single html file.
• should support both desktop and mobile screen sizes
• build with npm into single file with embedded content into css.

Please consider providing 1 manifest.yaml file for installing the operator, for usage with e.g. kustomize.