At the level of a container or two it is not really useful.

But if your load is high enough that you need hundreds of them, it becomes pretty great. Imagine you have a service that is big enough to have 20 pods of frontend, 20 pods of backend and 5 pods with database. You will want to have some kind of load-balancer for them, also you want to check that they all up and have the same configuration between them. You also want some internal network routing. Probably you want to gradually deploy updates. Probably you want some area where your devs can play around testing stuff. That’s where you need k8s, it does all this.

It has its price though - you need a separate server just to host k8s, actually you need three of them in case of hardware failures.

So, basically if your hw park is big enough that you can spare three hosts for management cluster, you probably want k8s. If it’s less, you can manage it with more manual means.

Well, this was the earliest appearance I could find

Oh cool! Your potato looks exactly like this potato from 7 years ago! What a world, huh

Nebius is doing it in Finland

Yes. Also, my llms can do it too

English, Russian, Serbo-Chroatian, a bit of Ukrainian. Very little of Deutsch.

The Goes Wrong Show.

“Illegal war”? Every war must be illegal