From 939c26f4475fbd9347f02ab95dd40b4744da67e4 Mon Sep 17 00:00:00 2001 From: chymy Date: Tue, 16 Mar 2021 10:52:05 +0800 Subject: [PATCH] Fix figure 1 not found Signed-off-by: chymy --- .../20190610-machine-states-preboot-bootstrapping.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/proposals/20190610-machine-states-preboot-bootstrapping.md b/docs/proposals/20190610-machine-states-preboot-bootstrapping.md index 8dccb1f2bf91..de7c9345a500 100644 --- a/docs/proposals/20190610-machine-states-preboot-bootstrapping.md +++ b/docs/proposals/20190610-machine-states-preboot-bootstrapping.md @@ -360,9 +360,9 @@ MachinePhaseFailed = MachinePhaseType("failed") #### Expectations - User intervention. -![Figure 1](./images/machine-states-preboot/Figure1.png) - --- +![Figure 1](../book/src/images/bootstrap-controller.png) + ### Sequence diagram: User creates a machine with Kubeadm bootstrapper. In this scenario, we go through each step from “kubectl apply” to seeing the Node in “Running” state. The user has chosen to create a Machine with the following: no custom user data, Machine.Bootstrap is a Kubeadm bootstrap provider, and Machine.InfrastructureRef is an AWS infrastructure provider.