Add message about possible problem when doing clusterctl move

kubernetes-sigs · Mar 9, 2020 · 4c949d6 · 4c949d6
1 parent 5f5e57f
commit 4c949d6
Showing 1 changed file with 3 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,6 @@ 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
+
+Please note that since the control plane nodes will have a `NoSchedule taint`, `clusterctl init` will not be able to schedule any pods and will timeout if the target cluster does not have any worker nodes.