-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Imperative api pls #434
Imperative api pls #434
Conversation
@bigkevmcd adding you since you had reviewed the other one previously. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
One thing I'd like to have as test in the future is running the API server with the APIService configured so that we can verify a few things when going through the main kubeapiserver (eg: ensuring user, groups and extras headers are properly propagated). This would require running a pod as an integration test (or potentially we can do that when RDP work is done).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
// NewUnionAuthenticator creates a [UnionAuthenticator]. | ||
// | ||
// The authenticators will be tried one by one, in the order they are given, until | ||
// one succeed or all fails. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"one succeeds or all fail" ??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I like the examples included in the comments.
rancher/rancher#47540
Replaces #316