Hi team,
When running aws-nuke, EKS cluster deletion fails with a 409 from the AWS EKS API:
operation error EKS: DeleteCluster, https response error StatusCode: 409, ResourceInUseException: Cluster has capabilities attached
Example resource (from nuke output):
eu-central-1 - EKSCluster - pg-backup-central-k8s - failed
It looks like this happens when the cluster has EKS managed capabilities attached (newer EKS feature). AWS won’t allow DeleteCluster until capabilities are removed (e.g. via aws eks list-capabilities / aws eks delete-capability).
Request: Could aws-nuke support cleaning up EKS cluster capabilities before calling DeleteCluster, or at least detect this specific error and print a clear hint (including the CLI commands) so users can unblock deletion?
Environment:
Resource type: EKSCluster
Error: 409 ResourceInUseException: Cluster has capabilities attached
If you want, I can provide full debug logs / versions (aws-nuke, AWS CLI, etc.).
Hi team,
When running aws-nuke, EKS cluster deletion fails with a 409 from the AWS EKS API:
operation error EKS: DeleteCluster, https response error StatusCode: 409, ResourceInUseException: Cluster has capabilities attachedExample resource (from nuke output):
eu-central-1 - EKSCluster - pg-backup-central-k8s - failed
It looks like this happens when the cluster has EKS managed capabilities attached (newer EKS feature). AWS won’t allow DeleteCluster until capabilities are removed (e.g. via aws eks list-capabilities / aws eks delete-capability).
Request: Could aws-nuke support cleaning up EKS cluster capabilities before calling DeleteCluster, or at least detect this specific error and print a clear hint (including the CLI commands) so users can unblock deletion?
Environment:
Resource type: EKSCluster
Error: 409 ResourceInUseException: Cluster has capabilities attached
If you want, I can provide full debug logs / versions (aws-nuke, AWS CLI, etc.).