Add message about possible problem when doing clusterctl move

Co-Authored-By: Vince Prignano <vince@vincepri.com>
kubernetes-sigs · Mar 9, 2020 · 1fd6930 · 1fd6930
1 parent 5f5e57f
commit 1fd6930
Showing 1 changed file with 4 additions and 1 deletion.
diff --git 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
+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.