From bb959bd1074a32be2ee39363b3184e32f25e0a6e Mon Sep 17 00:00:00 2001 From: John Gardiner Myers Date: Fri, 3 Jan 2020 20:08:47 -0800 Subject: [PATCH] Fix broken link --- docs/development/rolling_update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development/rolling_update.md b/docs/development/rolling_update.md index 97d7b9fd219bf..37b6d7db7c871 100644 --- a/docs/development/rolling_update.md +++ b/docs/development/rolling_update.md @@ -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.