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
t
tall-school-18125
09/14/2022, 3:19 PMWhat k8s distro is it? RKE2? Did you add it with a registration command?
g
gifted-branch-26934
09/14/2022, 3:29 PM@tall-school-18125 no just RKE (1), yes i added the node with a reg command from the cluster management tab
t
tall-school-18125
09/14/2022, 4:06 PMis the node template for the worker node the same as the node template for the other nodes?
g
gifted-branch-26934
09/14/2022, 4:06 PM@tall-school-18125 yes
t
tall-school-18125
09/14/2022, 4:17 PMwhat Rancher version is it?
g
gifted-branch-26934
09/14/2022, 4:18 PMv2.6.6
even after deleting the new node, the isse still happens. tried to upgrade external dns to latest version but still same error
actually also another 2 deployments got down at the same time and stuck with failed readiness probes...
the issue was fixed, i added again the clusterrolebinding and the service account and worked (no idea how really) as it was working fine before... thanks for the help!