Skip to content
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

Need to delete minikube-cluster,user,context config from kubeconfig file. #6538

Closed
anencore94 opened this issue Feb 7, 2020 · 0 comments · Fixed by #6541
Closed

Need to delete minikube-cluster,user,context config from kubeconfig file. #6538

anencore94 opened this issue Feb 7, 2020 · 0 comments · Fixed by #6541

Comments

@anencore94
Copy link
Contributor

anencore94 commented Feb 7, 2020

The exact command to reproduce the issue:

  1. cat $HOME/.kube/config and check the stdout.
    (Maybe the path will be different, it depends on your KUBECONFIG enviroment variable. I guess you already know.)

  2. minikube start (with or without -p option to specify profile)

  3. cat $HOME/.kube/config and recheck the stdout again. And compare with output of 1).

    • you can check the information about your new minikube instance's cluster, user, context added.
  4. minikube delete

  5. cat $HOME/.kube/config and recheck the stdout. And compare with output of 1), 3)

    • Added information in 3) remains.
    • I think the output of 5) needs to be same as 1). Not 3)
    • I think if minikube start set kubeconfig, minikube delete should unset kubeconfig.
  • I think there is this logic in the source code (func deleteContext in cmd/minikube/cmd/delete.go), but it won't actually works.

The full output of the command that failed:


NONE

The output of the minikube logs command:


NONE

The operating system version:

Ubuntu 18.04.4 LTS
minikube Version : tested with current master branch (commit: 9b7573e) binary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant