You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Fixed bootstrap failure rollback issue**: Removed WaitCondition dependencies from critical outputs to match original working architecture. Stack will still fail if bootstrap fails, but will rollback cleanly without orphaned resources.
19
+
## Architecture Fixes Applied
20
+
1.**Fixed bootstrap failure rollback issue**: Removed WaitCondition dependencies from critical outputs to match original working architecture. Stack will still fail if bootstrap fails, but will rollback cleanly without orphaned resources.
21
+
2.**Fixed EKS startup delay**: Refactored role creation to match original architecture - role is created in props and shared between IDE and EKS, eliminating CloudFormation dependency that delayed EKS cluster creation.
Copy file name to clipboardExpand all lines: .kiro/specs/infra/requirements.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,7 +184,7 @@ This document specifies the requirements for creating a new AWS workshop infrast
184
184
#### Acceptance Criteria
185
185
186
186
1. WHEN EKS cluster is created, THE system SHALL use the EKS v2 developer preview construct from package "software.amazon.awscdk.services.eks.v2.alpha" for native CloudFormation resource support
187
-
2. WHEN EKS cluster is created, THE system SHALL name it "workshop-cluster" for universal identification across workshop types
187
+
2. WHEN EKS cluster is created, THE system SHALL name it "workshop-eks" for universal identification across workshop types
188
188
3. WHEN EKS cluster is configured, THE system SHALL use version 1.34 for current Kubernetes features and security updates
189
189
4. WHEN EKS cluster deploys, THE system SHALL enable Auto Mode with "system" and "general-purpose" node pools for automatic node management
190
190
5. WHEN EKS cluster networking is configured, THE system SHALL place cluster in private subnets with public and private API access for security and flexibility
0 commit comments