This patch fixes the validation regression that rejected private-only clusters in 2.12.0.
New
- Private-only clusters validate again. A configuration with both
networking.public_network.ipv4andipv6set tofalsenow needs a private network andnetworking.ssh.use_private_ip: true. The validator no longer emits the unconditional "no public address is left to connect to" error that 2.12.0 added. The specific error remains when either requirement is missing. - by @deubert-it
Documentation
- The private-cluster guide now includes the required
networking.ssh.use_private_ip: truesetting, anddocs/Important_upgrade_notes.mdexplains the requirement for existing configurations.
Upgrading
If you run a cluster with both public address families disabled, set networking.ssh.use_private_ip: true before running create. 2.12.0 already required it; this release removes the redundant error and documents the setting, it does not change the requirement. Existing clusters with public IPv4 or IPv6 are unaffected.
No other configuration changes are needed. No bundled addon versions changed in this release.
Thanks
Thanks to @deubert-it for the fix and the detailed issue report.
Full changelog: v2.13.0...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!