-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS provider can't create an EKS cluster #436
Comments
well, that looks like a bug. We'll look into that |
In There are a couple bugs as well, but they can be worked around. EksCluster(self, "eks-cluster",
name = cluster_name,
role_arn = eksRole.arn,
vpc_config = [{
"endpointPublicAccess": True,
"subnetIds": mylist
}]
) |
This is working with this approach. Thanks for the clarification about the Typescript casing. Regards |
I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Community Note
cdktf & Language Versions
cdktf --version 0.0.18-pre.134
Affected Resource(s)
https://gist.github.com/cesarpball/5180bfadd8e1fb16116b810cb97b4530
Expected Behavior
EKS created successfully
Actual Behavior
Steps to Reproduce
cdktf diff
Important Factoids
subnet_ids is a valid input for Terraform on the EKS cluster creation. This value is receiving a list of subnets-ids: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_cluster
References
None
The text was updated successfully, but these errors were encountered: