Skip to content
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.

Sign up for GitHub

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

Jump to bottom

panic: no Auth Provider found for name "azure" #55

Closed
sethgupton-mastery opened this issue Mar 4, 2022 · 2 comments · Fixed by #57
Closed

panic: no Auth Provider found for name "azure" #55

sethgupton-mastery opened this issue Mar 4, 2022 · 2 comments · Fixed by #57
Labels
enhancement New feature or request

Comments

@sethgupton-mastery
Copy link
Contributor

I get this error when I switched over from using v1 to v2. I am using "Service Principal Authentication" and the same credentials as before.
@sethgupton-mastery sethgupton-mastery added the need-to-triage Requires investigation label Mar 4, 2022
@sethgupton-mastery
Copy link
Contributor Author

Oh. I think I found it. By default aks get-credentials gets the clusterUser role. We need the clusterAdmin role which is what v1.1 was getting.

Adding --admin to the command fixes it.

@OliverMKing OliverMKing mentioned this issue Mar 17, 2022
Merged
@OliverMKing OliverMKing added enhancement New feature or request and removed need-to-triage Requires investigation labels Mar 17, 2022
@sethgupton-mastery
Copy link
Contributor Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add subscription and admin commands
2 participants
@OliverMKing @sethgupton-mastery