Add documentation and configuration for deploying Helm chart with oauth2-proxy #851
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explains how to add oauth2-proxy as a dependency of an umbrella Helm chart, allowing the web front end and API to be served behind a reverse proxy that redirects unauthenticated traffic to the auth provider.
According to Jake (Filik), passing the
Authorization
header into the application requires using the unstable alphaConfig. I'd like to find a nicer way of handling the oauth2-proxy -> tiled service name mapping.Parking here momentarily until authentication can be revisited.
Checklist