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
a
acoustic-pharmacist-59341
07/12/2022, 10:08 PMHi, I was just curiously trying to bootstrap a test cluster with elemental via iPXE. I have a single node that came up with v1.22.10+k3s1 and started to cluster-init but it's stuck waiting for kube-controller-manager to come up. However, k3s-server isn't listening on port 10252 like it expecst.
Hmm, it appears that the probe is looking at 10252 but it’s only listening on 10257. But according to this issue, this is solved?
https://github.com/rancher/rancher/issues/35683