-
Notifications
You must be signed in to change notification settings - Fork 93
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
Can't connnect to kubernetes: Unauthorized
error when using aws-iam-authenticator
#19
Comments
Can't connnect to kubernetes: Unauthorized
error when using aws-iam-authenticator
Apologies, I can see this is fixed in master! |
Hi @coryodaniel, thanks for the report!
Hmm, it's working for you? Nice! |
Yeah its working great, any chance of building a 0.6.1 with the suppoert for |
The only difference between I wonder what's going on here? Maybe it's a golang version issue? The binary is built with |
I'm running Heads up, I am absolutely no Go jedi! Is there any output that could be helpful? |
I also ran into this issue with the 0.6.0 release when trying to communicate with an AWS EKS cluster:
I was able to get things working locally by updating the k8s.io/client-go package and its dependencies to 1.11.2, which has support for the
Hope this helps! |
Thanks, @dgarbus, that's really helpful. |
I have been using this tool (and its fantastic) for the past week or so. I recently moved to the aws-iam-authenticator and it now returns the error above.
I saw an older related ticket and fix (#2). It seem to just be adding the GCP auth pluging.
aws-iam-authenticator is handled through
exec
so maybe just adding the following will work?https://github.com/kubernetes/client-go/blob/master/plugin/pkg/client/auth/exec/exec.go
I'm curious if there is a way for it to work with all supported authentication strategies. Based on the files in that
auth
directory, I assume people using OIDC have the same issue?Version: 0.6.0 (e2ee089)
The text was updated successfully, but these errors were encountered: