feat: Add cloudformation describe stack step on create cluster failure #4556
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for karpenter-docs-prod canceled.
|
aman0408
commented
Sep 7, 2023
website/content/en/preview/getting-started/getting-started-with-karpenter/createec2.yaml
Outdated
Show resolved
Hide resolved
aman0408
force-pushed
the
describe-stack-events
branch
from
bf25606
to
8a7d632
Compare
aman0408
force-pushed
the
describe-stack-events
branch
from
8a7d632
to
4feabad
Compare
aman0408
force-pushed
the
describe-stack-events
branch
from
41d7f4f
to
5fcaa59
Compare
aman0408
force-pushed
the
describe-stack-events
branch
from
533db64
to
271dd11
Compare
jonathan-innis
approved these changes
Sep 8, 2023
|
Snapshot successfully published to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #4467
Description
Added a new step in E2E test workflow to describe cloudformation stack events on failure to "create eks cluster" step. This will enable us to view the failure reason in the logs itself.
How was this change tested?
Ran E2E workflow while ensuring the create eks cluster step failed. Also tried creating a dummy ec2 stack creation and made it fail.
Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.