Update managed-node-update-behavior.adoc#1229
Open
aksyadav wants to merge 1 commit intoawsdocs:mainlinefrom
Open
Update managed-node-update-behavior.adoc#1229aksyadav wants to merge 1 commit intoawsdocs:mainlinefrom
aksyadav wants to merge 1 commit intoawsdocs:mainlinefrom
Conversation
Made the following changes under the 'The _default_update strategy' section: 1. Added a point in line number 88 which explains that all old nodes gets cordons once the new node comes in Ready state. This happens by design but the step indicating the same was missing and caused confusion for the customer. 2. Modified line 91 and stated that the cordoned and drained node wait for 60 seconds before termination. As earlier it stated that the cordoning of the old node happens after draining, which is not true. Proposing the above changes based on the feedback from the customer
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Made the following changes under the 'The _default_update strategy' section:
Added a point in line number 88 which explains that all old nodes gets cordons once the new node comes in Ready state. This happens by design but the step indicating the same was missing and caused confusion for the customer.
Modified line 91 and stated that the cordoned and drained node wait for 60 seconds before termination.
As earlier it stated that the cordoning of the old node happens after draining, which is not true.
Proposing the above changes based on the feedback from the customer
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.