Only downside seems to be the Performance of tunnels in Containers.
I use them for my personal Website, did a bit of Loadtesting and was able to get significantly more RPS without the CF Tunnel. Might be something on my end tho, not sure.
That's interesting. Cloudflare tunnels do a few things that I expected to to make it perform better in general: obviously TLS termination on CF's side where they likely have faster hardware doing that (at least faster than many customers), then the keep-alive sockets for tunnel<->CF, and I think they use UDP/QUIC for the tunnel<->CF connection[0] which I figure could remove some latency.
Could you please elaborate how and what you know about managed Kubernetes on Hetzner?
I am asking for this since a while and was told there is no way Hetzner would offer such a service. Certain Posts on Social Media have also never been answered with any kind of indication that they are actually working on it.
They were in person recruiting at KubeCon EU this year and were advertising a good number of Kubernetes engineering roles. Definitely gave me the impression they were taking Kubernetes seriously but looking back a managed offering was just speculation on my part.
So huge grain of salt, you are totally right. It could be internal platform work only.
This is kinda the mental-cage I am in right now:
For some small amount of containers (300 at most, almost all webserver-like), I would like to have some basic high availability and scheduling on a few nodes. K8S, K3S and even Nomad feels overkill, I tried all of them. Swarm on the other hand is so easy so setup and get running, its seems like the perfect solution. The only thing stopping me is the stigma of Swarm being dead, which is not even the case right now (there is still support but no new features / communication). I feel like starting with swarm right now would be perfectly fine but using a technology which likely may be declared official dead in about 1-2 years, just some how feels wrong. This is my own mental-cage-issue here, right?
This is what I mean about how they FUDed themselves. There is a thing called swarm that isn't supported anymore but there's no reason to think the newer thing called swarm is gonna go away, and the only way I think it matters if it gets new "features" is if docker as a whole does. If it started collecting new features unique to swarm it'd just become another k8s.
This is my first time hearing about swarm and swarm ?
I always thought they killed it and brought it back zombie-style soon after. How can I distinguish between them? Like is there any way to make sure I use the new one? Is there documentation? Now you made me question reality :D
The messaging around this was terrible, but it's basically that a separate product got killed and they made it a core feature with the same name at the same time.
