Update strategies for managed node groups

Understand each phase of node updates Setup phase Scale up phase Upgrade phase PodEvictionFailure errors during the upgrade phase Scale down phase Help improve this page To contribute to this user guide, choose the Edit this page on GitHub link that is located in the right pane of every page. The Amazon EKS managed worker node upgrade strategy has four different phases described in the following sections. The setup phase has these steps: It creates a new Amazon EC2 launch template version for the Auto Scaling Group that’s associated with your node group. The new launch template version uses the target AMI or a custom launch template version for the update. It creates a new Amazon EC2 launch template version for the Auto Scaling Group that’s associated with your node group. The new launch template version uses the target AMI or a custom launch template version for the update. It updates the Auto Scaling Group to use the latest launch template version. It determines the maximum quantity of nodes to upgrade in parallel using the updateConfig property for the node group. The maximum unavailable has a quota of 100 nodes. The default value is one node. For more information, see the updateConfig property in the Amazon EKS API Reference. It determines the maximum quantity of nodes to upgrade in parallel using the updateConfig property for the node group.