Skip to content
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

Jump to bottom

Fix broken link #8266

Merged
merged 1 commit into from
Jan 4, 2020
Merged

Fix broken link #8266

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 docs/development/rolling_update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ Upgrading and modifying a k8s cluster often requires the replacement of nodes.

When starting the rolling update, kops will check each instance in the instance group if it needs to be updated, so when you just update nodes, the master will not be updated. When your rolling update is interrupted and you run another rolling update, instances that have been updated before will not be updated again.

![Rolling Update Diagram](/development/images/rolling-update.png?raw=true "Rolling Updates Diagram")
![Rolling Update Diagram](images/rolling-update.png?raw=true "Rolling Updates Diagram")

`kops` executes steps 2-4 for all the masters until the masters are replaced. Then the same process is followed to replaces all nodes.