When trying to create a new DKP cluster, you might encounter an error that resembles the following:
✓ Waiting for cluster infrastructure to be ready
✓ Waiting for cluster control-planes to be ready
✓ Waiting for machines to be ready
✓ Initializing new CAPI components
✗ Moving cluster resources
error in moving resources: unable to pivot to the to-cluster: failed to get object graph: failed to check for provisioned infrastructure: [cannot start the move operation while the control plane for "/, Kind=" default/aws-my-cluster is not yet initialized, cannot start the move operation while "/, Kind=" default/aws-my-cluster-xx-x-xxxxxxxxxx-xxxxx is still provisioning the node, cannot start the move operation while "/, Kind=" default/aws-my-cluster-control-plane-xxxxx is still provisioning the node, cannot start the move operation while "/, Kind=" default/aws-my-cluster-xx-x-xxxxxxxxxx-xxxxx is still provisioning the node, cannot start the move operation while "/, Kind=" default/aws-xxxx-cluster-x-x-xxxxxxxxxx-xxxxx is still provisioning the node, cannot start the move operation while "/, Kind=" default/aws-my-cluster-xx-x-xxxxxxxxxx-xxxxx is still provisioning the node]
This is usually a result of your local machine still having a bootstrap cluster running from a previous failed attempt. To resolve this, you can delete the current cluster and its resources (manually in the AWS console in some cases), then make sure you delete the bootstrap cluster:
./dkp delete bootstrap
After this, you can retry the "./dkp create cluster" operation again and it should resolve this error.