https://rancher.com/ logo
#rke2
Title
f

freezing-teacher-93828

09/05/2022, 8:49 AM
First post. In a high-availability RKE2 cluster (using kube-vip and 3 servers) should the file /etc/rancher/rke2/config.yaml be identical on the three servers (server1, server2, server3)? It seems to work although server1 lacks the lines for token: and the server: I did 1. Install server1 2. Install kube-vip 3. install server2 and server3 by adding two lines for token: and server: to the file /etc/rancher/rke2/config.yaml I am wondering if I should edit /etc/rancher/rke2/config.yaml on server1 to make it identical to the same file on the server2 and server3? Currently /etc/rancher/rke2/config.yaml on server2 looks something like this:
Copy code
token: masked
server: <https://cluster.example.com:9345>
tls-san:
- server2
- <http://server2.example.com|server2.example.com>
- <http://cluster.example.com|cluster.example.com>
- 12.34.56.78
disable: rke2-ingress-nginx
disable-kube-proxy: true
cni:
- cilium
(I masked the kubevip IP address and wrote 12.34.56.78 instead)
c

creamy-pencil-82913

09/05/2022, 9:07 AM
You can specify the token on all three if you want, or on none at all (as it’ll be read from the token file if not set in the config)
You can take the server out of the other two after they’ve joined the cluster, or you can add it to the first one. It’s basically ignored once the server joins the cluster, so do whatever you like.
f

freezing-teacher-93828

09/05/2022, 9:10 AM
I see, thanks for the informative answer!
28 Views