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
hetzner-k3s delete does not remove worker pool placement groups #321
Comments
Hi, yeah I'm aware of this and it's on my list of things to fix for the next release. Placement groups don't cost money nor cause any problems so I haven't given this higher priority. |
Not sure this is the right place to comment as this is about placement groups, but: I have set up a project and ran create/delete repeatedly (very cool stuff :) ). I also went through the README and found:
I would actually say that not deleting the LB can be quite a nice behaviour. When combining it together with something like Cloudflare DNS it avoids reconfiguring the IP in CF. I guess the default should be to delete it as people may run into unexpected costs, but perhaps this behaviour (not deleting the LB) could be supported through a flag. |
The README doesn't expand on this but the idea is to ask the user for a confirmation before deleting load balancers and persistent volumes, so you can choose :) |
Hi! When running
hetzner-k3s delete
, it uses the wrong names when it refers to the names of the worker pool placement groups that were created. On creation, the placement groups get namedname-X
, whereX
is a number. That number is not being used during the deletion process, so the placement groups remain and need to be deleted by hand using the cloud console.So for example, with a config snippet as follows:
During creation, the output confirms the creation like this:
And deletion fails like this:
The text was updated successfully, but these errors were encountered: