-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
eks: Unable to create fargate clusters #26289
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
Comments
Gum-Christopher-bah
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Jul 7, 2023
github-actions
bot
added
the
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
label
Jul 7, 2023
Closing, I needed to add |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
Describe the bug
Attempting to create an eks fargate cluster fails during the Custom::AWSCDK-EKS-Cluster creation step, stating that a cluster already exists with that name. Attempted on the following aws-cdk-lib versions (cdk cli tool also set to corresponding version): 2.78.0, 2.80.0, 2.83.0, 2.86.0, 2.87.0. Previously (At the time of the cdk version's release) I was able to deploy a fargate cluster using CDK version 2.54.0, which added support for EKS version 1.24, using the same account and local deployment role I'm using now. Re-bootstrapped account to latest as well to rule that out.
Expected Behavior
Able to create new clusters using latest CDK version
Current Behavior
Error:
The log group above contains 2 streams, one with a timestamp of 12:22 that shows the cluster is in a creating state:
And another at 12:38 where it calls onCreate a second time and fails
Reproduction Steps
Create a stack with just a cluster in a file
Deploy it with an app in another file
Where
existing_vpc
is a vpc referenced from lookup in the app using default context to get account/regionPossible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.87.0, 2.86.0, 2.83.0, 2.80.0, 2.78.0
Framework Version
No response
Node.js Version
v18.13.0
OS
Mac
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: