This message was deleted.
# harvester
a
This message was deleted.
b
that's odd, one of my nodes does not have an rke2.yaml hv03:/home/rancher # kubectl get nodes W0713 140059.510168 28150 loader.go:223] Config not found: /etc/rancher/rke2/rke2.yaml The connection to the server localhost:8080 was refused - did you specify the right host or port? hv03:/home/rancher # cd /etc/rancher/rke2 hv03:/etc/rancher/rke2 # cat rke2.yaml cat: rke2.yaml: No such file or directory hv03:/etc/rancher/rke2 # ls config.yaml.d
a
I had a similar issue due to my not having static IPs (or static DHCP leases) on the hosts. The underlying K8s did not like the IP changes that occurred after the hard power cycle. I ended up rebuilding and assigning static DHCP reservations for the servers so it would not happen again.
b
all static. This is all lab while I learn kubernetes. I think I will just bare-metal it until v2
👍 1
g
might be good to check if the rancher/harvester pods are running?