-
Notifications
You must be signed in to change notification settings - Fork 40
[Fix] Create-VPC stack to attach subnets for EKS cluster #1875
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
[Fix] Create-VPC stack to attach subnets for EKS cluster #1875
Conversation
Signed-off-by: Jugal Chauhan <[email protected]>
Signed-off-by: Jugal Chauhan <[email protected]>
Signed-off-by: Jugal Chauhan <[email protected]>
7cbff5b
to
5fbd4c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this deployment, it failed before, now it works.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1875 +/- ##
============================
============================
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
This PR fixes the EKS VPC stack creation failure in
Migration-Assistant-Infra-Create-VPC-v3
by ensuring subnet IDs are properly provided during EKS cluster creation.When no explicit
vpcSubnetIds
were passed, only private subnets were included in the subnetIds list, causing EKS cluster creation to fail in certain networking configurations. This caused the stack creation to fail :Resource handler returned message: "Subnet Id is required (Service: Eks, Status Code: 400)"
Issues Resolved
No Jira
Testing
CFN Stack is CREATE_COMPLETE
Executed using command :
Check List
- [ ] New functionality includes testing- [ ] Public documentation issue/PR created, if applicable.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.