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
As reported in a k0sctl issue, k0s always uses os.Hostname() as the etcd --name value. Maybe the value should be replicated from --kubelet-extra-args="--hostname-override=..."?
The text was updated successfully, but these errors were encountered:
The kubelet runs on workers, not on controllers. So this could only meaningfully apply to controller+worker nodes. Moreover, the os.Hostname() is also used in some other places, i.e. for events emitted by k0s. I agree, the node name handling in k0s is a bit messy and scattered around in many places, including autopilot. Fixing this would require some thought, though.
Is this a cosmetic thing, or would this fix a real problem?
What happened?
As reported in a k0sctl issue, k0s always uses
os.Hostname()
as the etcd--name
value. Maybe the value should be replicated from--kubelet-extra-args="--hostname-override=..."
?The text was updated successfully, but these errors were encountered: