This message was deleted.

Just to confirm, you deleted the control plane nodes from your cluster?

yes I did. I followed the guide mentioned above for the DR

Maybe, in your case, manual certificate rotation would have helped. See https://docs.rke2.io/security/certificates . You should never delete all the control plane nodes. The cluster basically is the control plane.

thanks but Certificate rotation is not an issue anymore. its the issue of nodes not being able to add to the cluster

Well, I was trying to tell you, that, technically, you don't have a cluster anymore after deleting all the control plane nodes. And you also didn't say something about a backup that you kept outside of the control plane nodes. Delete the workers and start over!

oh yes you are right that the cluster doesn't exist anymore. what I am curious about is the possibility to force these worker nodes to be a part of same rancher cluster instance. even though i have to start over.

The cluster instance is just a bunch of yaml in Rancher. See it as a blueprint of the actual cluster. The configuration, workload etc. is not persisted in Rancher but on the control plane nodes in etcd. Rancher is the management instance. A normal cluster (with control plane nodes) is continuing to work if you switch off Rancher.

yes thats what i did. I restored the etcd snapshot on one of the node with all the roles and re-attached all the nodes (even the worker nodes without loosing any data). But its independent of rancher. What I actually need is to attach the new cluster to the same old rancher cluster instance which I had before because it is being managed by code. is there any way to do it?

If it was really provisioned by Rancher, I don't know any way. You can detach it, remove it from Rancher and import it again, but then it's just an imported cluster. Check the docs for differences.