New
- Private-only Kubernetes API load balancer. The new
disable_public_interface_for_the_kubernetes_api_load_balancersetting, off by default, disables the public interface of the API load balancer so that the Kubernetes API is reachable only over the private network. Hetzner firewalls do not apply to load balancers, so until now a cluster with an API load balancer answered on port 6443 from the internet whatevernetworking.allowed_networks.apisaid. - @pkieszcz- The kubeconfig, the masters' TLS SANs and the worker join URL all use the load balancer's private IP, and the kubeconfig selects the load balancer context as soon as it is written.
- A newly created load balancer has no public interface. An existing one is made private in place, after
createchecks that it is attached to the cluster's private network and that every target uses private IPs. If a check fails, or the load balancer has no targets,createstops before changing anything and asks for the load balancer to be deleted so that it is recreated. - Covered in the cluster creation guide, the private-cluster guide and the upgrade notes.
Improvements
- The private-API check now also rejects a load balancer that has no targets, rather than disabling its public interface and leaving the API unreachable through it.
Upgrading
No action is required. The setting is off by default, and an existing cluster keeps its current load balancer, TLS SANs and join address until it sets the flag.
Enabling it on an existing cluster takes one maintenance window. The load balancer address in the masters' --tls-san changes from its public IP to its private IP, so the next create restarts k3s on the masters (the first master alone, then the others together, which on three masters is one short API outage) and restarts the k3s agent on every static worker once. Existing autoscaled nodes keep the old join address unless synchronise_autoscaled_nodes is on or the autoscaler replaces them, and with join_via_api_server_hostname the name has to resolve to a private address first. create and kubectl then have to run from a machine that can reach the private network. Details are in the upgrade notes.
No addon versions changed in this release: the cloud controller manager, CSI driver, system upgrade controller and cluster-autoscaler pins are the same as in v2.13.1.
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! 🙏