-
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
panic: No Auth Provider found for name "oidc" #345
Comments
The format is
|
whoops, thank you! |
4 tasks
ripta
added a commit
to ripta/kops
that referenced
this issue
Jul 24, 2018
Without this change, kops connections using OIDC to the cluster will receive this error message: cannot build kube client for "$CLUSTER_NAME": No Auth Provider found for name "oidc" kubernetes/client-go#345 suggests importing `.../client/auth/oidc`. Looking at the code one level above, `.../client/auth` will actually handle loading all known auth plugins for us.
ripta
added a commit
to ripta/kops
that referenced
this issue
Jul 24, 2018
Without this change, for example, kops connections using OIDC to the cluster will receive this error message: > cannot build kube client for "$CLUSTER_NAME": No Auth Provider found > for name "oidc" kubernetes/client-go#345 suggests importing the package path `plugin/pkg/client/auth/oidc` from `client-go`, but looking at the code `plugin/pkg/client/auth` will actually handle loading all known auth plugins for us.
ripta
added a commit
to ripta/kops
that referenced
this issue
Jul 24, 2018
Without this change, for example, kops connections using OIDC to the cluster will receive this error message: > cannot build kube client for "$CLUSTER_NAME": No Auth Provider found > for name "oidc" kubernetes/client-go#345 suggests importing the package path `plugin/pkg/client/auth/oidc` from `client-go`, but looking at the code `plugin/pkg/client/auth` will actually handle loading all known auth plugins for us.
ripta
added a commit
to ripta/kops
that referenced
this issue
Jul 25, 2018
Without this change, for example, kops connections using OIDC to the cluster will receive this error message: > cannot build kube client for "$CLUSTER_NAME": No Auth Provider found > for name "oidc" kubernetes/client-go#345 suggests importing the package path `plugin/pkg/client/auth/oidc` from `client-go`, but looking at the code `plugin/pkg/client/auth` will actually handle loading all known auth plugins for us.
HarikrishnanBalagopal
added a commit
to HarikrishnanBalagopal/move2kube
that referenced
this issue
Nov 14, 2020
client-go isn't properly importing openid connect. This causes the call to get an API client to fail always. Fix: add a blank import as suggested in the github issue: kubernetes/client-go#345 also refatored CLI by removing globals. Signed-off-by: Harikrishnan Balagopal <[email protected]>
HarikrishnanBalagopal
added a commit
to HarikrishnanBalagopal/move2kube
that referenced
this issue
Nov 14, 2020
client-go isn't properly importing openid connect. This causes the call to get an API client to fail always. Fix: add a blank import as suggested in the github issue: kubernetes/client-go#345 also refatored CLI by removing globals. Signed-off-by: Harikrishnan Balagopal <[email protected]>
ashokponkumar
pushed a commit
to konveyor/move2kube
that referenced
this issue
Nov 14, 2020
client-go isn't properly importing openid connect. This causes the call to get an API client to fail always. Fix: add a blank import as suggested in the github issue: kubernetes/client-go#345 also refatored CLI by removing globals. Signed-off-by: Harikrishnan Balagopal <[email protected]>
This was referenced Oct 5, 2023
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The out of cluster config example no longer works for me. I believe it was recently so I'm not sure what changed. I get this error:
I am able to list the nodes:
I tried doing coreos/tectonic-forum#99 (comment)
But then I just get this, as expected:
The text was updated successfully, but these errors were encountered: