Channels
extensions
rancher-extensions
sle
sle-bci
harvester-dev
neuvector-security
supermicro-sixsq
onlinetraining
office-hours
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
espanol
lima
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
rancher-setup
developer
mexico
random
elemental
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
s3gw
hobbyfarm
rancher-desktop
general
rke2
Powered by
#rke2
Title
c
creamy-pencil-82913
11/08/2022, 5:45 PM
check the logs on the first node to see why it’s not ready yet
check rke2-server and rancher-system-agent logs
g
gifted-eye-43916
11/09/2022, 11:02 AM
The node is "Ready" in the cluster, but not through Cluster management
Firewalld is off, just like SELinux. And I run the nodes in same subnet under Proxmox
Issue was old RKE2 rpm's which were installed in the nodes. case closed
3 Views
Post