This message was deleted.
# rke2a
adamant-kite-43734
09/26/2023, 1:54 AMThis message was deleted.
c
creamy-pencil-82913
09/26/2023, 4:13 AMInit node is only important to the rancher provisioning framework, which picks an node as the picks a primary node for others to join against. Nodes can join to any server equally.
r
rhythmic-boots-77358
09/26/2023, 4:45 AMThe problem I am facing is that we use custom machines for our control plane nodes, and if the "init node" is terminated (manually or via cloud provider) then any subsequent node cannot join the cluster.
Not sure if this should be opened as a bug?
rhythmic-boots-77358
09/26/2023, 4:46 AMI was hoping to build some automation that can be contextually aware of the init node, but seems thats not possible as it stands.
c
creamy-pencil-82913
09/26/2023, 4:55 AMThis is really more of a rancher issue than an rke2 issue, since the provisioning logic is all in Rancher. It does have code to re-select the init node, I believe you have to make sure it's deleted, and not just unavailable, though.
creamy-pencil-82913
09/26/2023, 4:55 AMLike, delete the machine from rancher
r
rhythmic-boots-77358
09/26/2023, 4:57 AMYeh this is why I was trying to programatically determine if the node was an init-node. Currently the node is being terminated outside of rancher, so from it's perspective it probably thinks that its just unavailable.