Skip to content

v2.12.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Sep 22:03
2.12.0
6ccf1a9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Add `force_update_version` and `replace_node_group_on_version_update` variables @aknysh (#151)

what

  • Add force_update_version and replace_node_group_on_version_update variables

why

  • force_update_version allows forcing version update if existing pods are unable to be drained due to a pod disruption budget issue. Default is false for backwards compatibility

  • If the variable replace_node_group_on_version_update is set to true and 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 the force_update_version variable. This is related, for example, to istio. Default is false for backwards compatibility

references

Contributors

aknysh
Assets 2
Loading