Closed pigletfly closed 5 years ago
@astefanutti any idea when this bug is gonna be fixed ?
@cscetbon I'll try to have it fixed for the next release.
I haven't been able to reproduce though it seems it's caused by a kube config file having a context with user
that cannot be found in the users
section by name. Would you be able to share your kube config file or confirm that hypothesis?
@astefanutti, I use kubeadm-dind-cluster in my case and yeah there is no user used at all. Here is my configuration file
apiVersion: v1
clusters:
- cluster:
insecure-skip-tls-verify: true
server: http://127.0.0.1:32772
name: dind
contexts:
- context:
cluster: dind
namespace: cassandra-e2e
user: ""
name: dind
current-context: dind
kind: Config
preferences: {}
@cscetbon thanks, that helps. I'll fix it for the next release.
It should be fixed with 483a00ad61e40bb2e027d1ec68d5457705bb4d2d.
when I run kubebox in a kubernetes cluster without certificate,a error was raised: