Add support to set up an OIDC proxy in the chart #968
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prydonius
approved these changes
Feb 22, 2019
|
@prydonius I have added a bit of documentation to cover the chart options to set the OIDC proxy, please take a look and let me know if you have any suggestions, I can do that in a follow-up PR. |
|
@andresmgot looks good, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #949
Changes in the chart that allow users to install an OIDC proxy (keycloak-gatekeeper) with the Kubeapps chart. The proxy is run as a sidecar container in the frontend deployment.
I am waiting for #967 to be landed before adding some documentation about how this can be used in the document
using-an-OIDC-provider.md.This PR is ready to be reviewed but should not be merged until a new version of Kubeapps is available.