Fail to delete a VPC if an EKS cluster was created in it about provider-aws

[muvaf]

The root cause for this was a race condition regarding routetable and it has been fixed for quite a while now. If you experience this, feel free to reopen.

[rafaeldomi]

I can confirm this situation. The following scenario, all in one composition:

1. Create VPC, Subnets, IGW, NG
2. Create a Role for EKS, EKSCluster, NodeGroups, Addons: EBS CSI Driver, core-dns, Kubeproxy, VPC-CNI

When I remove this composition, take a while to all resources get removed (sometimes because of the race condition). But EKS create a Network Interface that is not known by crossplane, so the removal of the VPC get stuck with the error that has dependencies.

Removing, manually, the ENI solves the problem.

How I would normally solve this?
Create a ENI in my composition and reference that resource in the EKS. But there isn't this field in the EKS Cluster.

What I NOT want to do?
To remove it manually, break the purpose of the automation.

crossplane version: 1.10.2
provider crossplane-aws version: 0.36.1