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

kubeone reset: add delete k8s generated cloud resources like Load Balancers and PVs #3394

Open
toschneck opened this issue Sep 25, 2024 · 1 comment
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.

Comments

@toschneck
Copy link
Member

Description of the feature you would like to add / User story

As a kubeone user
I would like to clean up my environment and delete all kubeone created resources, inkluding the LBs and Volumes what may are created within the Kubernetes Cluster
in order to have a clean environment after kubeone reset

Solution details

Currently (at least at AWS) the loadbalancer get not deleted before the control planes get destroyed. So they will stay for manual cleanup. Therfore it would be good to have a similar flag as --destroy-workers e..g --destory-cloud-resources what cleans up:

  • Load Balancers
  • Persistent Volumes

Alternative approaches

Use cases

Clean environment after kubeone reset.

Additional information

@toschneck toschneck added kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Sep 25, 2024
@rajaSahil
Copy link
Contributor

rajaSahil commented Nov 21, 2024

I can work on this, assigning it to me. Thanks @xmudrii for giving an overview.
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Development

No branches or pull requests

2 participants