iso

yeah, you pretty much described the use case for k8s. It allows for rapid horizontal scaling, since you can easily throw another machine into the cluster if you need it. It mostly makes sense if you actually have multiple machines sitting idle to begin with, so this technology is mostly used in combination with managed quick rent servers (think AWS).

Beyond that, k8s is kinda fancy for cluster management, but if you don't have a cluster you kinda don't need it to begin with. Using simple kernel VMs (think Proxmox) or just Docker works better there. You could still go for k8s since it's pretty much docker with cluster functionalities, just in case you want to expand eventually (sidenote, docker allows for cluster functionalities too, but they put a price on it, while k8s is open source iirc).

In that company I worked, k8s was considered but ultimately not implemented since it was considered a bit overkill. We already had everything set up with a bunch of bash scripts anyway, so it didn't matter too greatly to begin with.

Just to add some more background on this: I used to work tightly with the Network Team in the website team of the biggest contender in its market (can't disclose which one without people figuring out the company since the market is a bit niche).

We had 20'000 Users a day with a lot of images served.

The whole infrastructure consisted of 2 Firewall servers and the main DB (pSQL) on 2 self-hosted servers (think colo, it was sitting in a very remote location with 2 big diesel generators that would've ran the whole datacenter for a week iirc), with 14 Hetzner backend mirrors who ran the whole PHP code, served images and the angular + some weird custom Javascript. Scaling was done by simply throwing more Hetzners at it.

Given that Lemmy runs super performance efficient in comparison to 20 year deprecated PHP code that held together with ducttape, I feel like much less could make it work.

I'm glad you moved away from AWS, I wouldn't even consider going for VM hosting and would've gone dedicated from the get go (or even self-hosting on a colo / using a good fiber connection at home, but I guess I live in a super privileged country when it comes to ISPs).

Isn't k8s a bit overkill tho? Front-loaded caching seems to make sense, but a single 10gbit dedi could probably resolve the issue easier and simpler, couldn't it?

Du kannst Hunde und Katzen heutzutage komplett vegan ernähren. Gibt veganes Tierfutter spezifisch für diese Tiere.

Bei anderen Tieren ists obviously bisschen schwieriger

You should stop refering to middle school biology and check out university biology. And maybe also stop refering to outdated knowledge that's been disproven.

I feel you, I've been super active in a niche community of a game ( /r/ADCmains from League), and even though it was a salty shitshow, I enjoyed it there.

I got some of that fixed by joining a discord, but it's not the same :/

I'm suffering through Jerboa, heavily anticipating Sync since it'll change everything for me

I assume you've onky checked the massively overloaded kbin.social instance? Or is it a general issue with kbin itself?

WoW places. Since some of my servers died, I'm currently only sitting on dark portal (Firewall), and the Stranglethorn Valley server with Gurubashi Arena (Plex), Booty Bay (you can imagine) and wild shore (shared file system VM)

I think so. That, as well as putting /home on a different partition in order to just replace the OS but not lose data

So the only thing helping would be VPN + DNS change... not too easy, but not too hard either to be honest, but it will probably exclude a lot of people from access

damn that's pretty genius, although, doesn't the tin foil or the pocket between the window heat up?