Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
h
handsome-monitor-68857
02/27/2023, 4:14 PMMy 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-schedulera
acoustic-addition-45641
02/27/2023, 6:05 PMDepending 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 AMIf you are using ubuntu, you will need to install iptableshttps://docs.harvesterhci.io/v1.1/rancher/node/rke2-cluster#create-rke2-kubernetes-cluster
h
handsome-monitor-68857
02/28/2023, 1:23 AMIn 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 AMYou can try using a cni other than calico and not using the cloud provider and see if that works