You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using k3s with version >= v1.23.x I get this error when spinning up the cloud controller (which blocks any other component due to the cloud controller readiness taint):
cloud-controller-manager
I1124 09:28:48.381554 1 serving.go:313] Generated self-signed cert in-memory
cloud-controller-manager
failed to create listener: failed to listen on 0.0.0.0:10258: listen tcp 0.0.0.0:10258: bind: address already in use
When using k3s with version >= v1.23.x I get this error when spinning up the cloud controller (which blocks any other component due to the cloud controller readiness taint):
Turns out this is caused by a change in k3s k3s-io/k3s#6554
I tested the workaround mentioned in that ticket by manually editing
/etc/rancher/k3s/config.yaml
A quick look at the server config schema doesn't reveal any trick I can use to set that arg:
should I add
KubeCloudControllerManagerArgs
?The text was updated successfully, but these errors were encountered: