[aws-eks] Circular dependency exist when deploying EKS FargateCluster

[tmokmss]

I cannot deploy EKS FargateCluster because of circular dependency.

Reproduction Steps

CDK code

import * as eks from '@aws-cdk/aws-eks';
import * as cdk from '@aws-cdk/core';

export class EksTestStack extends cdk.Stack {
  constructor(scope: cdk.App, id: string, props?: cdk.StackProps) {
    super(scope, id, props);

    const cluster = new eks.FargateCluster(this, 'cluster', {
      version: eks.KubernetesVersion.V1_17,
    })
  }
}

and deploy by the command below:

npm run cdk deploy EksTestStack

What did you expect to happen?

deployment succeeds

What actually happened?

The error below occurs:

 EksTestStack (eks-test) failed: Error [ValidationError]: Circular dependency between resources: 
[clusterRole88D0C969, clusterDefaultVpcVPCGWB52AB94D, clusterMastersRoleEABFBB9C, clusterDefaultVpcPublicSubnet3NATGateway5D6BCE9C, clusterDefaultVpcPrivateSubnet1RouteTableAssociation941EEF5E, clusterDefaultVpcIGWEA83F638, clusterDefaultVpcPublicSubnet3SubnetCF380ECB, clusterfargateprofiledefault40EAF542, clusterDefaultVpcPrivateSubnet3RouteTable68FAA6DE, clusterfargateprofiledefaultPodExecutionRoleB7B70029, awscdkawseksKubectlProviderNestedStackawscdkawseksKubectlProviderNestedStackResourceA7AEBA6B, clusterDefaultVpcPublicSubnet2NATGateway4B5BF1A3, clusterKubectlReadyBarrier17584D5B, clusterDefaultVpcPublicSubnet1RouteTableAssociationF21DD285, clusterControlPlaneSecurityGroup7F1D5AB2, clusterDefaultVpcPrivateSubnet2RouteTable9A709948, clusterDefaultVpcPublicSubnet3RouteTableDF03BEAA, clusterDefaultVpcPrivateSubnet3RouteTableAssociation1051D4E6, clusterCreationRoleDefaultPolicy69503D2C, awscdkawseksClusterResourceProviderNestedStackawscdkawseksClusterResourceProviderNestedStackResource9827C454, clusterDefaultVpcPublicSubnet3DefaultRoute6DFF6152, clusterDefaultVpcPrivateSubnet2DefaultRoute29031EDD, clusterDefaultVpcPrivateSubnet3SubnetB16AB70B, clusterDefaultVpcPublicSubnet1DefaultRoute008A2768, clusterDefaultVpcPrivateSubnet1DefaultRoute1A3591A8, clusterDefaultVpcPublicSubnet2SubnetD89F8A7D, clusterDefaultVpcPrivateSubnet1RouteTable6588FE09, clusterAwsAuthmanifestB57F2A94, clusterDefaultVpc83B86FBD, clusterDefaultVpcPrivateSubnet1Subnet56973734, clusterDefaultVpcPrivateSubnet2Subnet3A49BF39, clusterDefaultVpcPublicSubnet2RouteTable4B281F43, clusterDefaultVpcPublicSubnet1RouteTableFD55F525, clusterCoreDnsComputeTypePatchE0553C88, clusterDefaultVpcPublicSubnet2DefaultRoute3C6354F6, clusterCreationRole2B3B5002, clusterDefaultVpcPrivateSubnet3DefaultRouteFE3587F6, clusterDefaultVpcPublicSubnet2EIP92893124, clusterDefaultVpcPublicSubnet3EIP3576AE12, clusterDefaultVpcPublicSubnet1Subnet6A0D5072, clusterDefaultVpcPublicSubnet1EIP0E34F4D0, clusterDefaultVpcPublicSubnet1NATGateway3F34F14E, clusterDefaultVpcPublicSubnet2RouteTableAssociation8D159B16, clusterDefaultVpcPrivateSubnet2RouteTableAssociation188551CD, clusterDefaultVpcPublicSubnet3RouteTableAssociationEC89C4A6, clusterC5B25D0D]

Environment

• CLI Version : 1.64.0
• Framework Version: 1.64.0
• Node.js Version: v13.11.0
• OS : macOS
• Language (Version): TypeScript

Other

---

This is 🐛 Bug Report

[tmokmss]

succeeded in deploying when using cdk 1.61.0.
It seems there's a problem somewhere between 1.62.0 to 1.64.0.

[iliapolo]

@tmokmss Thanks for reporting this. We are investigating a fix and we'll update here.