-
Notifications
You must be signed in to change notification settings - Fork 87
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
We need flags to delete all dependent resources and configurations with deleting a cluster #406
Comments
Can be a global one like --delete-dependent-resource that by default can be false and if you pass the api can delete all related object, we can use the same flag in terraform |
@alejandrojnm |
@uzaxirr no we don't have and even the UI is not deleting them. We had some conversation around it multiple times, but they never translated into a practical action. |
Hey @fernando-villalba @uzaxirr, I can solve this issue. Could you assign it to me? |
… deleting a cluster, addressing issue civo#406
I've submitted a pull request. Please review and let me know if any changes are required. |
Issue
Currently when you create and delete clusters, it leaves too many dependent resources and configuration behind, for example:
Deleting all of these by hand or scripting it separately is very tedious
We need flags that delete these resources together with the cluster.
Acceptance Criteria
1. I suggest making the deletion of firewalls and kubeconfig the default, and keep volumes by default but provide option to get rid of them
After all, you can always revert your firewalls and config is only valid for that cluster, so no point in keeping them for the vast majority of cases.
And then have flags to delete the volumes that may have important data.
So you could have flags like this:
civo kubernetes delete --delete-volumes
--> Deletes dependent volumescivo kubernetes delete --keep-firewalls
--> keeps dependent firewallscivo kubernetes delete --keep-kubeconfig
--> keeps dependent firewalls2. When deleting clusters let the user know what was left behind
Aside outputting what cluster names and ids were deleted, also output the volumes that were left behind, and as an info message sent to stderr, you can mention the flag to delete dependent volumes next time.
The text was updated successfully, but these errors were encountered: