added nodegroup update config configuration#75
Open
amanravi-squareops wants to merge 1 commit intosquareops:release-5.4.3from
Open
added nodegroup update config configuration#75amanravi-squareops wants to merge 1 commit intosquareops:release-5.4.3from
amanravi-squareops wants to merge 1 commit intosquareops:release-5.4.3from
Conversation
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.
Configuration for the update strategy of the EKS managed node group.
max_unavailable_value: Defines how many nodes can be updated at a time.use_percentageistrue, this value represents the percentage of nodes that can be unavailable during updates.use_percentageisfalse, this value represents the absolute number of nodes that can be unavailable during updates.use_percentage: Determines whether
max_unavailable_valueshould be treated as a percentage or a fixed number.true:max_unavailable_valueis interpreted as a percentage (e.g., 50 means 50% of nodes can be unavailable).false:max_unavailable_valueis interpreted as an absolute number (e.g., 2 means 2 nodes can be unavailable).