2 Answers
- Newest
- Most votes
- Most comments
0
Hello, You need to remove the security group from the EFS network interface that is blocking the deletion. Ensure that the security group isn't actively being used by the node group anymore. You can manually detach it if necessary, before the removal of the NG.
Let me know if that works.
0
I faced the same issue, any solutions?
It's a dependecy loop:
[EKS cluster] -> [Node Group] -> [Security Group] -> [ENI (managed by EKS)]
Below are the details of my situation:
When I describe the ENI permission, it shows the owner ID is 392771493575 which must be the internal account owned by EKS:
james@hwdell:~$ aws ec2 describe-network-interface-permissions --output=json
{
"NetworkInterfacePermissions": [
{
"NetworkInterfacePermissionId": "eni-perm-051ff65effd8d55ed0",
"NetworkInterfaceId": "eni-0fd2c1d13185e8d59",
"AwsAccountId": "392771493575",
"Permission": "INSTANCE-ATTACH",
"PermissionState": {
"State": "GRANTED"
}
},
{
"NetworkInterfacePermissionId": "eni-perm-0e33b7221a76ac3f9",
"NetworkInterfaceId": "eni-0dbed56f2261a4ba7",
"AwsAccountId": "392771493575",
"Permission": "INSTANCE-ATTACH",
"PermissionState": {
"State": "GRANTED"
}
}
]
}
answered a year ago
Relevant content
asked a year ago
asked 3 years ago
