-
Notifications
You must be signed in to change notification settings - Fork 98
Description
Issue
Currently when you create and delete clusters, it leaves too many dependent resources and configuration behind, for example:
- Firewalls
- Volumes (especially if creating apps)
- Kube config
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 volumes
civo kubernetes delete --keep-firewalls --> keeps dependent firewalls
civo kubernetes delete --keep-kubeconfig --> keeps dependent firewalls
2. 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.