Add force_update_version and replace_node_group_on_version_update variables
#151
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
|
/terratest |
|
/terratest |
|
/terratest |
|
/terratest |
aknysh
changed the title
force_update_version and include_kubernetes_version_in_keepers variablesforce_update_version and force_node_group_replacement variables
aknysh
changed the title
force_update_version and force_node_group_replacement variablesforce_update_version and replace_node_group_on_version_upodate variables
aknysh
changed the title
force_update_version and replace_node_group_on_version_upodate variablesforce_update_version and replace_node_group_on_version_update variables
|
/terratest |
Nuru
requested changes
Sep 26, 2023
Co-authored-by: Nuru <Nuru@users.noreply.github.com>
Co-authored-by: Nuru <Nuru@users.noreply.github.com>
|
/terratest |
Nuru
approved these changes
Sep 26, 2023
9 tasks
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.
what
force_update_versionandreplace_node_group_on_version_updatevariableswhy
force_update_versionallows forcing version update if existing pods are unable to be drained due to a pod disruption budget issue. Default isfalsefor backwards compatibilityIf the variable
replace_node_group_on_version_updateis set totrueand the EKS cluster is updated to a new Kubernetes version, the Node Groups will be replaced instead of updated in-place. This is useful when updating very old EKS clusters to a new Kubernetes version where some old releases prevent nodes from being drained (due to PodDisruptionBudget or taint/toleration issues), but replacing the Node Groups works without forcing the pods to leave the old nodes by using theforce_update_versionvariable. This is related, for example, toistio. Default isfalsefor backwards compatibilityreferences