AWS CDK for EKS Cluster (L2 construct) is creating additional and unwanted resources.

[eraybp]

I currently have CDK code that builds and deploys my EKS clusters using the CfnCluster L1 construct and this works as expected. However, I am attempting to move to the L2 construct for EKS and I have found that it is attempting to do more than I would like. It is spawning a nested stack and attempting (but failing) to deploy a Providerwaiterstatemachine; along with a few other items. Is there a way to suppress this or would I need to continue to use the L1 construct to maintain control over my stacks, roles, etc...?