aws_eks_cluster: Increase create timeout to 30 mins #8909
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that as reported in #5165, an EKS cluster frequently takes more to actually bring up than the default create timeout allows for. While the timeout is configurable, the default should be sufficient to actually provision a cluster in most cases.
This commit increases the default timeout to 30 minutes.
Fixes #5165.
Community Note
Release note for CHANGELOG: