Hetzner now supports private networking

[jamesfarrugia]

Maybe the guide can now streamline its network setup stage and use internal IPs and make it "abstract" in terms of networks? (i.e. the part about having to use public IPs in Hetzner could be removed, making the process and guide simpler)

It is still beta though, so it might be best to wait until they finalise it
https://www.hetzner.com/cloud

[codeagencybe]

@jamesfarrugia
actually, the networks feature just got out of beta today. I just logged in and got the confirmation popup immediately that networks is now globally available.

[pstadler]

Hey guys. Currently really busy, having a newborn at home. Will catch up as soon as possible. Of course, this is great news, but I’d like to keep WireGuard in place to have a common secure networking option out of the box across different providers.

[pstadler]

Thanks a lot for supporting this project on Patreon @jamesfarrugia 😍

[jamesfarrugia]

First of all, congrats! I only wanted to point it out since just like @codeagencybe I got the popup today. I feel like wireguard should remain there as well yes, the main change would be in making it work pretty much in the same way as DO or SW.

It's my pleasure to at least acknowledge that this is a genuinely helpful project, I wish I could do more!

[codeagencybe]

@pstadler Congratulations! Hopefully you still have good sleep nights ;)
Enjoy the time because they grow so fast!

[osx2000]

Just a short note: I tried to get the private network feature to work - using the hcloud_server_network resource - but got stuck. Simply put, the "non-etcd-nodes" weren't able to connect to the etc master.