We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
example kubeconfig leveraging oidc against dex:
apiVersion: v1 clusters: - cluster: certificate-authority: /home/dcooley/ca-px-prd1002.pem server: https://k8s-api.v.k8s.work:6443 name: px-prd1002 contexts: - context: cluster: px-prd1002 namespace: identity user: qa@k8s.work name: px-prd1002 current-context: px-prd1002 kind: Config preferences: {} users: - name: qa@k8s.work user: auth-provider: config: client-id: gangway client-secret: supersecret id-token: <redacted> idp-issuer-url: https://identity.v.k8s.work/identity refresh-token: <redacted> name: oidc
gets me:
$ kubectl -n identity plugin scan deployment/dex panic: No Auth Provider found for name "oidc" goroutine 1 [running]: github.com/stefanprodan/kubectl-kubesec/vendor/k8s.io/client-go/kubernetes/typed/admissionregistration/v1alpha1.NewForConfigOrDie(0xc420171340, 0xc4202e0690) /home/travis/gopath/src/github.com/stefanprodan/kubectl-kubesec/vendor/k8s.io/client-go/kubernetes/typed/admissionregistration/v1alpha1/admissionregistration_client.go:60 +0x65 github.com/stefanprodan/kubectl-kubesec/vendor/k8s.io/client-go/kubernetes.NewForConfigOrDie(0xc420171340, 0x10c42e0) /home/travis/gopath/src/github.com/stefanprodan/kubectl-kubesec/vendor/k8s.io/client-go/kubernetes/clientset.go:529 +0x49 main.loadConfig(0x7ffd6b549f3c, 0xe, 0xfdce16) /home/travis/gopath/src/github.com/stefanprodan/kubectl-kubesec/main.go:136 +0x4e main.main() /home/travis/gopath/src/github.com/stefanprodan/kubectl-kubesec/main.go:45 +0xbf error: exit status 2
If I create an serviceaccount and generate a kubeconfig using it's token things work fine.
The text was updated successfully, but these errors were encountered:
Hi @mauilion
What Kubernetes version are you using?
Sorry, something went wrong.
v1.10.3 in this case
Successfully merging a pull request may close this issue.
example kubeconfig leveraging oidc against dex:
gets me:
If I create an serviceaccount and generate a kubeconfig using it's token things work fine.
The text was updated successfully, but these errors were encountered: