OpenID Connect auth support #663
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
Add the oidc plugin wherever gcp is added.
|
I think |
|
Thanks - I've pushed the updated lock file. |
jessesuen
approved these changes
Jan 8, 2018
icecoffee531
pushed a commit
to icecoffee531/argo-workflows
that referenced
this pull request
Jan 5, 2022
…loses argoproj#663. (argoproj#664) * feat: add affinity, tolerations in template and clusterIP in service * correct order
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.
Add OpenID Connect authentication support by loading the relevant auth plugin wherever the gce one is loaded.
My organisation runs Kubernetes with Keycloak as an OpenID Connect Identity Provider. There are a variety of other common options supported by this plugin - see https://kubernetes.io/docs/admin/authentication/#option-1---oidc-authenticator.
I've now successfully installed argo and run a hello-world workflow on such a cluster. Previously the install failed as it wasn't possible to authenticate.
I haven't looked into how auth works for argoexec / workflow-controller, so I've just followed the gce pattern there.