docs: Update migration guide to add not for increased NodeClaimNotFou… #6734
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!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Pull Request Test Coverage Report for Build 10391730934Details
💛 - Coveralls |
engedaam
reviewed
Aug 14, 2024
|
@jigisha620 Can we update the PR description as well -- looks like the title for the PR got too long |
jigisha620
force-pushed
the
docs-update
branch
3 times, most recently
from
8b9c170
to
50197bf
Compare
njtran
previously approved these changes
Aug 14, 2024
jigisha620
force-pushed
the
docs-update
branch
from
50197bf
to
4c73954
Compare
jigisha620
force-pushed
the
docs-update
branch
from
4c73954
to
da35a2d
Compare
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.
…ndError
Fixes #N/A
Description
Karpenter will waits for the underlying instance to be completely terminated before deleting a node and orchestrates this by emitting
NodeClaimNotFoundError. With this change we expect to see an increase in theNodeClaimNotFoundError. Documented this in the upgrade guide.How was this change tested?
NA
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.