Skip to content
This repository has been archived by the owner on May 24, 2022. It is now read-only.

Comprehensive garbage collection #4

Open
mhausenblas opened this issue Jul 6, 2019 · 1 comment
Open

Comprehensive garbage collection #4

mhausenblas opened this issue Jul 6, 2019 · 1 comment
Assignees
@mhausenblas
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@mhausenblas
Copy link
Owner

mhausenblas commented Jul 6, 2019 •
edited
Loading

Currently, on tear-down, cluster external resources are not automatically destroyed. For example, when you create a service of type LoadBalancer and don't delete it before the cluster is destroyed, the LB will continue to run.

So, this issue is about adding comprehensive garbage collection for external resources such as IAM policies and role attached after creation, networking gear (ELB, ALB, NLB, ENIs), storage (EBS volumes), and more. Could be based on tags (of the CF stacks, not EKS) and resource groups or heuristics. See also the informal survey.
@mhausenblas mhausenblas self-assigned this Jul 6, 2019
@mhausenblas mhausenblas added enhancement New feature or request help wanted Extra attention is needed labels Jul 6, 2019
@mhausenblas
Copy link
Owner Author

Will be done upstream in eksctl, see eksctl-io/eksctl#103 and eksctl-io/eksctl#1032

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mhausenblas mhausenblas

Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mhausenblas