-
-
Notifications
You must be signed in to change notification settings - Fork 462
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
k3d delete
fails when cluster has custom name
#54
Comments
Appreciate the bug report @nunix Which version of k3d are you running? you can get it from k3d --version. Any chance you can try to build k3d from the tip of master and try again? There were some refactoring in this area. I was not able reproduce this with a master build. I am on MACos, but this does not look to be a platform specific issue... |
Thanks for opening the issue. |
@nunix, I was able to replicate it with version 1.1.0 as well. The issue should have been fixed on the master. @iwilltry42 will make a release soon. With v1.1.0, there is an easier work around: 'k3d delete --all' |
oh ok perfect, will “play” with it a lot more during kubecon 😁 If needed/wanted this case can be closed or I will close upon new release with a last screenshot confirming the fix |
Just released v1.2.0, you may want to try it with this one 👍 |
Haha, no worries, I also didn't catch the typo in your screenshots 😁 |
first of all, incredible piece of software and being the WSL Corsair I had to test it on ... WSL 😈
everything works just fine, however if I create a cluster with a custom name (i.e.
k3d create --name wslk3d
), then when runningk3d delete
without any name, it will delete the$HOME/.config/k3d
directory, but not delete the cluster itself (see screenshot below)In the screenshot there's also the workaround
mkdir -p $HOME/.config/k3d/<cluster name>
Hope this helps and really looking forward to play with it ⭐️
The text was updated successfully, but these errors were encountered: