This message was deleted.

I found one workaround 1 remove taints from node 1 to allow all to be deployed and wait until worker node joined and then return taints back. Please let me know if it's fine and will not create any issues in the future?

kubectl taint nodes cluster-2-master-1 <http://node-role.kubernetes.io/control-plane-|node-role.kubernetes.io/control-plane-> <http://node-role.kubernetes.io/etcd-|node-role.kubernetes.io/etcd->

kubectl taint nodes cluster-2-master-1 <http://node-role.kubernetes.io/control-plane:NoSchedule|node-role.kubernetes.io/control-plane:NoSchedule> <http://node-role.kubernetes.io/etcd:NoExecute|node-role.kubernetes.io/etcd:NoExecute>

In the Rancher UI, disable tainting the server nodes