Skip to content

Update managed-node-update-behavior.adoc #1229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aksyadav wants to merge 1 commit into
base: mainline
Choose a base branch
from
Open

Update managed-node-update-behavior.adoc #1229

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion latest/ug/nodes/managed-node-update-behavior.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,10 @@ The minimal strategy is useful in scenarios where you are constrained to resourc
The _default_ update strategy has these steps:

. It increases the quantity of nodes (desired count) in the Auto Scaling Group, causing the node group to create additional nodes.
. It cordons all the old nodes of the node group as soon as a new node comes into 'Ready' state.
. It randomly selects a node that needs to be upgraded, up to the maximum unavailable configured for the node group.
. It drains the Pods from the node. If the Pods don't leave the node within 15 minutes and there's no force flag, the upgrade phase fails with a `PodEvictionFailure` error. For this scenario, you can apply the force flag with the `update-nodegroup-version` request to delete the Pods.
. It cordons the node after every Pod is evicted and waits for 60 seconds. This is done so that the service controller doesn't send any new requests to this node and removes this node from its list of active nodes.
. The cordoned and drained node waits for 60 seconds after the eviction of all the Pods from the node. This is done so that the service controller doesn't send any new requests to this node and removes this node from its list of active nodes.
. It sends a termination request to the Auto Scaling Group for the cordoned node.
. It repeats the previous upgrade steps until there are no nodes in the node group that are deployed with the earlier version of the launch template.

Expand Down