Skip to content
This repository was archived by the owner on Nov 3, 2023. It is now read-only.

kubectl buildkit create fails with no Auth Provider found for name "azure" error #129

Closed
gnadaban opened this issue Mar 23, 2022 · 0 comments · Fixed by #130
Closed

kubectl buildkit create fails with no Auth Provider found for name "azure" error #129

gnadaban opened this issue Mar 23, 2022 · 0 comments · Fixed by #130

Comments

@gnadaban
Copy link

What steps did you take and what happened
Attempted to create a buildkit instance as described in example on a cluster using Azure authentication.
What did you expect to happen

The command to succeed. Kubectl commands have no problem using the azure provider.

Environment Details:

  • kubectl buildkit version : 0.1.5
  • Kubernetes version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:30:48Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:32:02Z", GoVersion:"go1.17.7", Compiler:"gc", Platform:"linux/amd64"}
  • Where are you running kubernetes: Azure via cluster-api
  • Container Runtime and version: Containerd
Client:
  Version:  v1.6.0
  Revision: 39259a8f35919a0d02c9ecc2871ddd6ccf6a7c6e
  Go version: go1.17.2

Server:
  Version:  v1.6.0
  Revision: 39259a8f35919a0d02c9ecc2871ddd6ccf6a7c6e
  UUID: f43ebc8f-48e8-41e3-a161-457e414ac4dc

Builder Logs
N/A

Dockerfile
N/A

Vote on this request

This is an invitation to the community to vote on issues. Use the "smiley face" up to the right of this comment to vote.

  • 👍 "I would like to see this bug fixed as soon as possible"
  • 👎 "There are more important bugs to focus on right now"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant