Rancher Suite K8S Adventure - Chapter 009 - Rancher Cluster Additional Nodes Install

Rancher Suite K8S Adventure - Chapter 009 - Rancher Cluster Additional Nodes Install

A travelogue of converting from OpenStack to Suse's Rancher Suite for K8S including RKE2, Harvester, kubectl, helm.

Now its time to connect the remaining nodes to the first node, which was configured yesterday.  Server nodes are schedulable on RKE2, and it takes three RKE2 server nodes for HA, and coincidentally I have exactly three mini servers allocated to this project, so my cluster design is three servers, zero agents.

Second and subsequent members of a cluster install process:

# curl -sfL https://get.rke2.io | INSTALL_RKE2_VERSION="v1.24.10+rke2r1" sh -

Now, create a micro-mini config just enough to bootstrap:

mkdir -p /etc/rancher/rke2/

cat node-token >> /etc/rancher/rke2/config.yaml

vi /etc/rancher/rke2/config.yaml

server: https://<server>:9345

token: move that first line here

# systemctl enable rke2-server.service

# systemctl start rke2-server.service

(Insert an extremely dramatic very long pause here, about nine minutes?)

Eventually these two commands will settle down and look normal:

systemctl status rke2-server

journalctl -u rke2-server -f

(Repeat above for all future additional nodes in your cluster)

Some fun commands to try:

kubectl get node

kubectl get pods --all-namespaces

At this point you should have a stable three (or more?) node RKE2 cluster ready to run K8S workloads.

Tomorrow, "cert-manager"