Skip to content

Fix typo: 'most' to 'must' in node bootstrap requirements #1187

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
thecosmicfrog wants to merge 1 commit into
base: mainline
Choose a base branch
from
Open

Fix typo: 'most' to 'must' in node bootstrap requirements #1187

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
2 changes: 1 addition & 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 @@ -70,7 +70,7 @@ Custom user data can sometimes break the bootstrap process. This scenario can le
*Any changes which make a node unhealthy or not ready*::
Node disk pressure, memory pressure, and similar conditions can lead to a node not going to `Ready` state.

*Each node most bootstrap within 15 minutes*::
*Each node must bootstrap within 15 minutes*::
If any node takes more than 15 minutes to bootstrap and join the cluster, it will cause the upgrade to time out. This is the total runtime for bootstrapping a new node measured from when a new node is required to when it joins the cluster. When upgrading a managed node group, the time counter starts as soon as the Auto Scaling Group size increases.


Expand Down