join_via_api_server_hostname lets workers join through api_server_hostname instead of the first master's IP, so a cluster without an API load balancer can still add nodes while the first master is down.
New
join_via_api_server_hostname. With the setting on, static and autoscaled workers join throughapi_server_hostname, which is already in the masters' TLS SANs. It wins over the API load balancer if both are present, and external nodes still join the first master. Off by default. The name must resolve on the nodes, through DNS or the root-leveladditional_pre_k3s_commands; the docs cover that order and whatsynchronise_autoscaled_nodesdoes to existing autoscaled nodes. - by @michal-billtech
Upgrading
No action is required. The setting defaults to false, so existing clusters render the same worker and master scripts. Enabling it on a running cluster restarts k3s-agent on the static workers; adding api_server_hostname at the same time restarts k3s on every master, the first alone and then the others together. See docs/Creating_a_cluster.md for the details and the recommended order.
No bundled addon versions changed in this release.
Thanks
Thanks to @michal-billtech for the feature, the docs and the offline tests.
Full changelog: v2.12.0...v2.13.0
If hetzner-k3s is useful to you or your company, please consider sponsoring its development.
Sponsorship helps ensure continued maintenance and new features. Thank you to our current sponsors!