From 1fd69308fe9a83e3f63d95da65e8321f6d7ede86 Mon Sep 17 00:00:00 2001 From: Nader Ziada Date: Mon, 9 Mar 2020 09:35:53 -0400 Subject: [PATCH] Add message about possible problem when doing clusterctl move Co-Authored-By: Vince Prignano --- docs/book/src/clusterctl/commands/move.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/book/src/clusterctl/commands/move.md b/docs/book/src/clusterctl/commands/move.md index 5c85e598ade9..fa2e163e165d 100644 --- a/docs/book/src/clusterctl/commands/move.md +++ b/docs/book/src/clusterctl/commands/move.md @@ -60,4 +60,7 @@ This can now be achieved with the following procedure: 5. Get the kubeconfig for the new target management cluster 6. Use `clusterctl init` with the new cluster's kubeconfig to install the provider components 7. Use `clusterctl move` to move the Cluster API resources from the bootstrap cluster to the target management cluster -8. Delete the bootstrap cluster \ No newline at end of file +8. Delete the bootstrap cluster + +> Note: It's required to have at least one worker node to schedule Cluster API workloads (i.e. controllers). +> A cluster with a single control plane node won't be sufficient due to the `NoSchedule` taint. If a worker node isn't available, `clusterctl init` will timeout.