-
Notifications
You must be signed in to change notification settings - Fork 292
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
Port exec-based client auth provider to DotNet client #135
Comments
If it helps at all, I implemented this a while back for KubeClient. Happy to contribute my implementation if it'd be useful. https://github.com/tintoy/dotnet-kube-client/blob/27926d62bf48897837042b624412889fb7b5cdb1/src/KubeClient.Extensions.KubeConfig/K8sConfig.cs#L195 CC: @brendandburns |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Would be nice to have an implementation of this. I'm not sure of a work around to connect to EKS (fairly popular I think?) out-of- cluster without it |
With 1.10, this exec-based client auth credential provider alpha feature was introduced kubernetes/features#541 for client-go. Exec-based auth plugin should be supported by this DotNet client in addition to client-go. Umbrella issue: kubernetes#62185
/kind feature
/sig api-machinery
The text was updated successfully, but these errors were encountered: