This message was deleted.
# harvester
a
This message was deleted.
👍 1
s
Hi @rapid-iron-53423, what role would you like to change? Could you elaborate more?
r
Hi @salmon-city-57654, thanks for getting back on this. role of the Harvester Node. As we added more nodes, Management nodes are now compute nodes and some compute nodes are management nodes. We want to control which nodes can be Management Nodes for Harvester Cluster.
> Hi @salmon-city-57654, thanks for getting back on this. role of the Harvester Node. As we added more nodes, Management nodes are now compute nodes and some compute nodes are management nodes. We want to control which nodes can be Management Nodes for Harvester Cluster. Bumping this up in case anyone else has any idea to promote the node to Management manually.
b
If you use kubectl to get nodes, then edit one, you cna change these roles. I am not sure if it is the right place or not, but would be a good start.
Copy code
<http://node-role.kubernetes.io/control-plane|node-role.kubernetes.io/control-plane>: "true"
    <http://node-role.kubernetes.io/etcd|node-role.kubernetes.io/etcd>: "true"
    <http://node-role.kubernetes.io/master|node-role.kubernetes.io/master>: "true"
r
Yeah, i found this code and controller. It doesn’t get rid of etcd even you remove the label from rest of the nodes
s
Hi @rapid-iron-53423, did you mean you would like to promote the specific node to master?
r
Yes @salmon-city-57654,
ManagementNode
in Harvester Cluster. We started the cluster with nodes that we wanted as `ManagementNode`s in Harvester cluster, as we were testing disaster recovery scenario it switched to other nodes that we don’t to be ManagementNode. Also, as mike suggested i tried adding and removing labels
s
Now, we only promote the worker node to the master node at the first three nodes. Could you help to create a GH issue for this?
I thought you could manually modify the node label as @brainy-whale-97450’s suggestions. That should be worked.
r
Yeah, that worked partially, as i shared in the screenshot etcd still stays on all the nodes
s
I thought that’s a good point. We need to provide a way to let users change the node roles.
r
I will open GH issue with more details to troubleshoot or a possible documentation as there is already controller which is responsible for upgrading the node roles.
👍 2
s
Actually, we are working on a similar concept. hope we can give enough mechanisms for the DR design.
> I will open GH issue with more details to troubleshoot or a possible documentation as there is already controller which is responsible for upgrading the node roles. That would be great, thanks!
BTW, if you move a node to etcd. You might need to care about the taint. Or some workload would be deployed on it.
r
Actually, we are working on a similar concept. hope we can give enough mechanisms for the DR design.
Good to know. Is there something public that i can follow ?
s
We have a feature that will let the user set up the etcd (only) node when installation. This might introduce some mechanism to allow users to control the node role changing.
👍 1
r
BTW, if you move a node to etcd. You might need to care about the taint. Or some workload would be deployed on it.
yeah, we have sort of or tainted usage, as our Management Node does have some VM workloads primarily virtual network vms which we have tainted.
👍 1