Delete IAM Service Account before deleting CloudFormation Stack in Getting Starting guide #624
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 ready! 🔨 Explore the source changes: 6e6eb8d 🔍 Inspect the deploy log: https://app.netlify.com/sites/karpenter-docs-prod/deploys/611d49c1bdc21f00071017cb 😎 Browse the preview: https://deploy-preview-624--karpenter-docs-prod.netlify.app |
ellistarn
reviewed
Aug 18, 2021
| @@ -229,6 +229,8 @@ kubectl delete node $NODE_NAME | |||
| To avoid additional charges, remove the demo infrastructure from your AWS account. | |||
|
|
|||
| ```bash | |||
| helm uninstall karpenter --namespace karpenter | |||
There was a problem hiding this comment.
Why do we need to uninstall karpenter if we're deleting the cluster?
There was a problem hiding this comment.
I'm not 100% certain that it is necessary, but the helm chart uses the IAM Service Account and I wanted to avoid the dependency blocking the deletion of the IAM Service Account.
There was a problem hiding this comment.
Certainly doesn't hurt, just adds a few seconds.
ellistarn
reviewed
Aug 18, 2021
| @@ -229,6 +229,8 @@ kubectl delete node $NODE_NAME | |||
| To avoid additional charges, remove the demo infrastructure from your AWS account. | |||
|
|
|||
| ```bash | |||
| helm uninstall karpenter --namespace karpenter | |||
| eksctl delete iamserviceaccount --cluster ${CLUSTER_NAME} --name karpenter --namespace karpenter | |||
ellistarn
approved these changes
Aug 18, 2021
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.
Issue, if available:
Description of problem:
See https://karpenter.sh/docs/getting-started/#cleanup
The command
aws cloudformation delete-stack [...]succeeds on the command line but in the AWS Console the CloudFormation Stack's status changes toDELETE_FAILEDwith the reasonThe following resource(s) failed to delete: [KarpenterControllerPolicy].The policy is used by the IAM Service Account created manually during the setup.Description of change:
Before attempting to delete the CloudFormation Stack:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.