adamant-kite-43734
10/25/2024, 1:20 PMwitty-jelly-95845
10/25/2024, 2:55 PMrefined-smartphone-93179
10/25/2024, 2:57 PMwitty-jelly-95845
10/25/2024, 2:58 PMrefined-smartphone-93179
10/25/2024, 2:58 PMrefined-smartphone-93179
10/25/2024, 2:59 PMwitty-jelly-95845
10/25/2024, 3:00 PMrefined-smartphone-93179
10/25/2024, 3:01 PMx.x.x.x
vs
<https://x.x.x.x>
?
not sure if that mattersrefined-smartphone-93179
10/25/2024, 3:04 PMwitty-jelly-95845
10/25/2024, 3:05 PMrefined-smartphone-93179
10/25/2024, 3:16 PMcurl -k <https://harvester.local/ping>
and it resolves fine (this is node 1 mgmt url)witty-jelly-95845
10/25/2024, 3:21 PMrefined-smartphone-93179
10/25/2024, 3:21 PMwitty-jelly-95845
10/25/2024, 3:23 PMwitty-jelly-95845
10/25/2024, 3:24 PMrefined-smartphone-93179
10/25/2024, 3:27 PMcouldnt get current server API group list: GET <https://127.0.0.1:6443> was refused
hard to know if that is even related since i see a similar error on the master node but with port 8080witty-jelly-95845
10/25/2024, 3:29 PMrefined-smartphone-93179
10/25/2024, 3:32 PMharvester01:~ # kubectl get nodes -n harvester-system
NAME STATUS ROLES AGE VERSION
harvester01 Ready control-plane,etcd,master 108d v1.28.12+rke2r1
harvester02 NotReady <none> 69m v1.28.12+rke2r1
This is interesting... so node 1 is actually seeing node 2 but not finishing setting it uprefined-smartphone-93179
10/28/2024, 3:53 PMwitty-jelly-95845
10/29/2024, 10:30 PMwitty-jelly-95845
10/29/2024, 10:31 PMwitty-jelly-95845
10/29/2024, 10:34 PM