Newly added node will not join as master

[pfaelzerchen]

I originally started with a 3-node HA cluster. All three nodes were master nodes. Then I had to drain one of the nodes (track in the example) and replaced it. When I wanted to add the replaced node with

/usr/local/bin/k3s server --server https://tick:6443 --config /etc/rancher/k3s/config.yaml --token-file /etc/rancher/k3s/cluster-token

The newly created node joined, but not as master. kubectl get nodes gives the following result:

NAME    STATUS   ROLES                       AGE    VERSION
tick    Ready    control-plane,etcd,master   184d   v1.34.6+k3s1
track   Ready    control-plane,etcd          45m    v1.34.6+k3s1
trick   Ready    control-plane,etcd,master   185d   v1.34.6+k3s1

The node has a plain install with the current Ubuntu LTS Server.

Any hint for me what might be going wrong here?

[brandond]

Master node role has been deprecated for a long, long time. Starting with 1.34 new nodes will not be labeled as master. You can add it by hand if you want, but I'd probably go the other way and remove it from your existing nodes.

For more background see:

• Remove references to master node-role label and taints/tolerations #11117

[pfaelzerchen]

Thanks for the quick response.