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

EKS nuke should first identify nodegroups attached to the EKS cluster. #148

Closed
andrewpsp opened this issue Nov 1, 2020 · 3 comments
Closed
Labels
enhancement New feature or request p:queued

Comments

@andrewpsp
Copy link

Since the EKS cluster has nodegroups attached to the target cluster, the nuking fails for this resource with ResourceInUseException. This is a request to also delete nodegroups prior to destroying the EKS cluster.

INFO[2020-11-01T15:26:06-05:00] Deleting 1 EKS clusters in region us-west-2  
ERRO[2020-11-01T15:26:07-05:00] [Failed] Failed deleting EKS cluster wordpress-cluster: ResourceInUseException: Cluster has nodegroups attached
	status code: 409, request id: 86e9a981-019b-48d3-ad0e-31dc892e21ef 
INFO[2020-11-01T15:26:07-05:00] [OK] 0 of 1 EKS cluster(s) deleted in us-west-2 

@brikis98 brikis98 added enhancement New feature or request help wanted labels Nov 2, 2020
@brikis98
Copy link
Member

brikis98 commented Nov 2, 2020

That would indeed be helpful. I'm not sure when we'll get to it, so a PR is very welcome!

@yorinasub17
Copy link
Contributor

Also related is #111 (Fargate profiles). Would be nice to implement both at once.

@yorinasub17
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p:queued
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants