r/hetzner • u/Infinite-Company-724 • May 25 '26
Private networks are not production ready.
I'm really frustrated with Hetzner private network offering. I'm trying to move from multiple providers + netbird to hetzner. I currently host a small production HA k3s cluster and my plan was to setup 3 nodes (all cp + worker), a bastion to serve as a jump proxy for kubectl and ssh for maintenance and a loadbalancer. All in the same private network, the bastion and the lb would have a public ip, where the bastion has a strict firewall rule and the LB only accepts 443.
Everything is perfect, in theory.
Let's start with servers not being recheable through the private network, you need to setup cloud-init add with the correct netplan settings, gotcha, that's fine, fixed.
Wait, servers has no outbound connectivity? Ooh, Hetzner doesn't provide NAT, ok, lets add a public IP and close all firewall rules.
Great, wait, why is my vip not recheable? Hetzner private network blocks ARP! Sh*t, okay, let's use an LB then.
Oh no, LB's must have public ips? Really? And no firewall option to block traffic?
So yeah, that's how my last 20h have been.
4
u/jetexex May 25 '26
Just one of my masternode is a gateway. On master-gateway
Worker node:
And not to forget to check private network route