v2.6.0

New

• Introduced support for external nodes in addition to Hetzner cloud instances. These nodes can either be Hetzner dedicated servers managed by the Hetzner Robot interface, or generic nodes from any provider. In either case, all that is needed is SSH access to the nodes. hetzner-k3s will then set up these nodes just like the others. There is a limitation currently, in that these nodes are only supported with clusters not using the Hetzner private networks. In a future release, I'll add support for that case as well (Robot servers only though since nodes from other providers cannot access the Hetzner private networks). See the docs for more details.
• Introduced a new config setting named config_format_version currently defaulting to 1. This will help avoid problems in the future if a user tries to use an older version of hetzner-k3s with a given config file, by mistake.
• Reintroduced support for placement groups with a more robust implementation
• Added a new config setting cluster_domain to configure the domain name for the cluster. - by @an-tex

Fixes

• Addressed Issue #701 (#701) - Cluster Autoscaler emits repeated warning events due to missing gitlab-registry imagePullSecret
• The tool now longer adds the --kube-proxy-arg setting for k3s if kube proxy is disabled
• Added #!/bin/bash shebang so PIPESTATUS works under dash - by @baixianger
• Skip WireGuard mesh interfaces (NetBird, Tailscale, wg) in private network detection - by @VadimTrufyn

Improvements

Misc updates

• Upgraded Hetzner CSI Driver to v2.21.2
• Upgraded Hetzner Cloud Controller Manager to v1.33.0

Upgrading

• You will be requested to set config_format_version in the config file to 1 if it's missing.

---

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! 🙏