Network problem on node pool workloads-1 with access to the attached network about cluster-api-provider-hetzner HOT 3 CLOSED

ok then i will close this issue. ;)

from cluster-api-provider-hetzner.

@BigBrather without going too much into details, I can only tell you from my experience: we used hcloud networks in the beginning three years ago, since we started our managed kubernetes on hetzner, we had so many problems that we stopped using it. Since then, I try it from time to time, but I still have those kinds of problems.

There are so many great solutions out there that use the zero trust principle and with that approach really everything in your infrastructure is going to be much more secure because you always have to think about it from a security perspective. For example, we do not use a hetzner firewall, we only use the cilium host firewall, which makes the management much easier, single pane of declarative configuration and not the problem of misconfiguration or external issues. For internal traffic, we use things like mTLS where appropriate, so you can also get workload attestation with the right tools and a lot more visibility.

from cluster-api-provider-hetzner.

@batistein Thanks for your reply.

We abandoned the local network and will observe how CAPI works in this version. Hope this solves it our network problem.

Regarding the firewall settings on the Hetzner Cloud side, it is also clear.

from cluster-api-provider-hetzner.