Add `force_update_version` and `replace_node_group_on_version_update` variables @aknysh (#151)
what
- Add
force_update_version
andreplace_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 isfalse
for backwards compatibility -
If the variable
replace_node_group_on_version_update
is set totrue
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 theforce_update_version
variable. This is related, for example, toistio
. Default isfalse
for backwards compatibility