-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Velero v1.12.0 has no auth provider found for name "oidc" #6933
Comments
See the related thread in Slack: https://kubernetes.slack.com/archives/C6VCGP4MT/p1695924642015059 |
We will take a look at this issue at CloudCasa. Please assign to @0x113. |
One solution that work for me:
And rebuild the CLI:
|
This import is present in v1.11.* in auth_providers.go file but is removed in v1.12.0 any reason for that? and the removal is intentional or by mistake? and when will this change be released in v1.12? |
I was able to reproduce the issue with the OIDC auth provider. Will create a Pull Request with a fix shortly. |
Great!! |
Sorry for the inconvenience, and thanks for reporting and fixing this issue. The needed file was deleted during fixing revive linter errors.
|
Issue #6933: Import auth provider plugins
What steps did you take and what happened:
Velero server version: v1.12.0
Velero client version: v1.12.0
Velero client was not able to connect to Velero server when the auth provider is "oidc"
Ran velero --version command and it threw an error "An error occurred: no Auth Provider found for name "oidc""
Velero v1.11.* are working fine when the auth provider is oidc but not working in v1.12.0
Upon debuggging I found out that pkg/client/auth_providers.go is present in v1.11.* but is removed in v1.12.0
v1.11.1 : https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/client/auth_providers.go
v1.12.0: https://github.com/vmware-tanzu/velero/tree/v1.12.0/pkg/client
What did you expect to happen:
Velero client should be able to connect to Velero server and should display the client and server versions
The following information will help us better understand what's going on:
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>
to generate the support bundle, and attach to this issue, more options please refer tovelero debug --help
If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
velero backup describe <backupname>
orkubectl get backup/<backupname> -n velero -o yaml
velero backup logs <backupname>
velero restore describe <restorename>
orkubectl get restore/<restorename> -n velero -o yaml
velero restore logs <restorename>
Anything else you would like to add:
Environment:
velero version
):velero client config get features
):kubectl version
):/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: