1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
2
As noted here, do you have any active services associated with LBs in your EKS cluster?
If so, you should delete those services through kubectl and wait until the LBs are deleted properly.
Also generally it is recommended you use eksctl, or ensure you followed the steps in the above page when deleting clusters.
As a last resort, you can try to delete the IGWs and resources, such as ELBs, within the VPC manually to resolve dependencies and clean up resources.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
Yes that is the case. Thanks for pointing that out. I actually discovered that by attempting to manually delete one of the VPCs, and noticed there were ENIs attached to it. However, the CloudFormation service could do a much better job of describing why the stack fails to delete.