This message was deleted.
# general
a
This message was deleted.
a
There is no easy way to do this (at least not that I know of. What you could try would be to 1. Create a new (custom) cluster 2. Reconnect rancher-system-agent with the rancher server on each of the nodes (beginning with the master node) (use a curl to connect to https://<rancher server>/v3/connect/agent specifying X-Cattle-Id, X-Cattle-Role-Etcd, X-Cattle-Control-Plane, X-Cattle-Role-Worker and such parameters in the header and a bearer token to authorize with.
l
Not sure how that would work... is this an alternative to doing an "Import" Not sure how the "in-between" would work since after you move one CP node, that endpoint is gone from the old cpu, and the new cluster would have a different endpoint and no other nodes
a
You need to perform this on all nodes. And yes, by creating a new cluster definition on the Rancher UI you would also create new cluster endpoints, but that is just the matter of changing some kubeconfig files. What I described is similar to what the installer does when creating a custom cluster but without the actual installation.