https://rancher.com/ logo
Title
h

handsome-monitor-68857

02/27/2023, 4:14 PM
My RKE2 cluster targeting on Harvester is not ready. It's stuck on provisioning as in below logs Where can I first to look into?
[INFO ] waiting for viable init node
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for agent to check in and apply initial plan
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, etcd, kube-apiserver
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, etcd, kube-apiserver
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, kubelet
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, kube-apiserver
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, etcd, kube-apiserver
[INFO ] configuring bootstrap node(s) cluster08-pool08-69c7d74894-776ff: waiting for probes: calico, kube-controller-manager, kube-scheduler
a

acoustic-addition-45641

02/27/2023, 6:05 PM
Depending on how you are targeting your Harvester instance, maybe related to this: https://github.com/harvester/harvester/issues/2590
f

full-plastic-79795

02/28/2023, 1:20 AM
h

handsome-monitor-68857

02/28/2023, 1:23 AM
In my setup, I created a uplink bond between each Harvester node and external networks, as below
I also used iptables in the Harvester nodes. It took a very long time for the Harvester cluster to come up
and after that, there are a lot of unhealth events
Is my network setup adding a performance penalty on the cluster? As above screenshot, kube-api-server and calico-kube-controllers are not really ready.
f

full-plastic-79795

02/28/2023, 1:49 AM
You can try using a cni other than calico and not using the cloud provider and see if that works