-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
[1.4.0] update-context: Kubeconfig does not have a record of the machine cluster #5497
Comments
Full output of
|
I too ran into this last week: for example, if you Ctrl-C Here's what we should make the code do, IMHO:
|
@tstromberg but |
@andrebraitc - Yes, that happens to me too. Edited my comment to clarify. |
I could also reproduce this issue(I think this always occurs). I think this is bug due to following code...
In minikube/pkg/minikube/kubeconfig/kubeconfig.go Lines 129 to 132 in 5c6f33b
However, the kubeconfig filepath is overwritten by machine name( I'll modify the way of getting kubeconfig filepath. |
/assign |
Tried with version 1.5.2 and the command crashes in the same way for me:
|
@lucanaldini |
@tstromberg how .kube/config to what? |
Works fine with 1.3.1.
I started fresh and removed the whole
.minikube
and.kube
directories from my user's home, since the last time I had troubles with minikube it was due to a corrupt ISO image.Running as my regular user. No
sudo
involved.The exact command to reproduce the issue:
minikube update-context
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version: Ubuntu 18.04
The text was updated successfully, but these errors were encountered: