Build failed due to "no Auth Provider found for name "oidc""

[LiYa-Xu]

What steps did you take and what happened

• Successfully installed buildkit
• Tried to do the same exact steps as in the example on a multiple nodes IKS cluster.
• When I try the command kubectl build -t pants -f Dockerfile ./, it's returned Error: no Auth Provider found for name "oidc"

What did you expect to happen Build image succeed Environment Details:

• kubectl buildkit version is v0.1.2
• Kubernetes version is v1.18.12+IKS
• Container Runtime and version

Client:
  Version:  1.3.7
  Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175

Server:
  Version:  1.3.7
  Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175
  UUID: 0bff7a7b-aa99-4e21-b290-b046a14820e5

Dockerfile git clone https://github.com/pdevine/pants.git

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.

• :+1: "I would like to see this bug fixed as soon as possible"
• :-1: "There are more important bugs to focus on right now"

[pdevine]

@LiYa-Xu are you using kubelogin and/or oidc-login with your kube cluster? You can check in ~/.kube/config

[LiYa-Xu]

@pdevine Thanks for you response, since I using the IKS cluster, so I export the KUBECONFIG, I think is same as kubelogin.

[LiYa-Xu]

@pdevine Any suggestions please?

[dhiltgen]

We just recently fixed Auth for GCP with https://github.com/vmware-tanzu/buildkit-cli-for-kubectl/pull/105/files and my suspicion is something similar is required for IKS. Since we don't really have a way to test this, PR's are welcome from someone who has access to IKS.

[clvx]

Having a similar issue using an OIDC system with plugin version 0.15.

//tried exporting KUBECONFIG and the following: 
kubectl buildkit --kubeconfig ~/.kube/config create 
Error: no Auth Provider found for name "oidc"