Skip to content

Commit

Permalink
Fix broken link
Browse files Browse the repository at this point in the history
  • Loading branch information
johngmyers committed Jan 4, 2020
1 parent 71761bf commit bb959bd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/development/rolling_update.md
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.

0 comments on commit bb959bd

Please sign in to comment.