EKS: Add Support for ServiceTimeout on all KubernetesManifest and HelmChart objects
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
Since a `CustomResource` underlies these, they should support the `ServiceTimeout` property so when a create or delete fails and doesn't cause an exception in the function, the CFN stack is not blocked for an hour waiting to fail.
### Use Case
When a create or delete fails and doesn't cause an exception in the function, the CFN stack is not blocked for an hour waiting to fail.
### Proposed Solution
In the `KubernetesManifest` props, add a `readonly serviceTimeout?: Duration;` property, and then set it in the `KubernetesManifest` constructor. Similarly, do the same for `HelmChart`.
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.170.1
### Environment details (OS name and version, etc.)
darwin
Contributor guide
Research direction
Start by locating the TypeScript EKS definitions and constructors for KubernetesManifest and HelmChart. Trace how CustomResource properties are exposed and configured, then verify that both objects accept and apply serviceTimeout for create and delete failures; no specific test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100