replace oauth2-proxy by louketo-proxy #2115
Closed
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.
Description of the change
This PR replaces oauth2-proxy by louketo-proxy (formerly known as keycloak-gatekeeper).
Benefits
Working integration with Keycloak
Possible drawbacks
Other providers are not tested and do not guaranteed that they will work
Applicable issues
Additional information
This PR provided just for example and does not pretend to be mergedю
Рowever until the better solution for #2111 is found, this is only working method to run kubeapps with internal oauth2 proxy service and Keycloak.