charts: Provide 3 options for oidc configuration #1920
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.
Now users have 3 different way they can set oidc configuration
Fixes: #1897
Testing
Scenario 1
This is when user just want to use ENV variables directly.
config.oidc.
clientID, clientSecret, issuerURL, scopes
invalues.yaml
and setconfig.oidc.secret
asfalse
helm template charts/headlamp
Scenario 2
This is when user wants to use external secret created by them
template/secret.yaml
. Then create it in your k8s cluster using kubectl command.config.oidc.secret
asfalse
and setconfig.oidc.externalSecret
astrue
and also the name of secret.helm template charts/headlamp
Scenario 3
This is when user want to use the secret created by headlamp
config.oidc.
clientID, clientSecret, issuerURL, scopes
invalues.yaml
and setconfig.oidc.secret
astrue
helm template charts/headlamp