-
Notifications
You must be signed in to change notification settings - Fork 3k
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
No Auth Provider found for name "gcp" #242
Comments
|
It seems you need import the auth plugin package
Is this working as intended? Is there any benefit to not loading auth plugins by default? |
Yes and this is documented in a couple places. The benefit is not overloading regular clients with unnecessary imports. E.g you don't have to import OpenID Connect and Azure packages. Going to close since it looks like this is working as intended. |
@ericchiang Can you point me to where it's documented? I just guessed based on reading the source code. It feels like that could be improved. Not that there are not really any "docs" to speak of yet. While I understand the need to avoid importing packages that aren't needed I question the wisdom of this a bit. I can see folks creating apps and integrations that don't work w/ GKE/Azure/Openid because they don't import the plugins. It feels weird to drop this all of a sudden since it worked in v2.0.0 and v3.0.0.beta.0 |
@ianlewis a few of the examples have lines like this
The actual change was made here kubernetes/kubernetes#41532 during the 1.6 release. Are you sure this changed between v3.0.0.beta.0 and v3.0.0? I'm not seeing them imported by default in v3.0.0.beta.0 https://github.com/kubernetes/client-go/blob/v3.0.0-beta.0/kubernetes/clientset.go I can add a changelog item for the v3.0.0.beta.0 |
@ericchiang I suppose you're right that it was removed between v2.0.0 and v3.0.0 but still the issue stands. |
More folks noticing this on twitter: https://twitter.com/davecheney/status/915770572017037312 |
FYI, I hit this error message, and the 2nd Google search result led me here. Glad this has the solution! |
When a gke cluster is targeted we get this error: No Auth Provider found for name "gcp" This commit fixes it. See also: kubernetes/client-go#242
When a gke cluster is targeted we get this error: No Auth Provider found for name "gcp" This commit fixes it. See also: kubernetes/client-go#242
* they needed the auth plugin import: _ "k8s.io/client-go/plugin/pkg/client/auth" * kubernetes/client-go#242
* they needed the auth plugin import: _ "k8s.io/client-go/plugin/pkg/client/auth" * kubernetes/client-go#242
For reference: kubernetes/client-go#242
Fixes No Auth Provider found for name "gcp" For reference: kubernetes/client-go#242
Fixes No Auth Provider found for name "gcp" For reference: kubernetes/client-go#242
Fixes No Auth Provider found for name "gcp" For reference: kubernetes/client-go#242
For the following code I get an error when trying to connect to a GKE API server with v3.0.0.
FWIW this worked in v3.0.0.beta.0
I have a version of apimachinery that's about 28 days old. Could it have to do with some library incompatibility?
The text was updated successfully, but these errors were encountered: