3 ms·

I think you are only looking at Kubernetes for running and updating container images. If that’s the use-case then I guess it’s overkill. But Kubernetes does mu

I think you are only looking at Kubernetes for running and updating container images. If that’s the use-case then I guess it’s overkill. But Kubernetes does much more in terms of providing the resources required for these containers to share state, connect to each other, get access to config or secrets etc. That’s where comes the CPU and memory cost. The cost of managing your containers and providing them the resources they need. > basically acts as a giant while loop Yep. That’s the idea of convergence of states I guess. In a distributed system you can’t always have all the participating systems behave in the desired way. So the manager (or orchestrator) of the system continuously tries to achieve the desired state.

jpc0 1y ago
> But Kubernetes does much more in terms of providing the resources required for these containers to share state, connect to each other, get access to config or secrets etc. This was OPs argument, and mine as well. My side project which is counting requests per minute or hour really doesn’t need that, however I need to eat the overhead of K8s just to have the nice dx of being able to push a container to a registry and it gets deployed automatically with no downtime. I don’t want to pay to host even a K3s node when my workload doesn’t even tickle a 1vCPU 256mb ram instance, but I also don’t want to build some custom scaffold to so the work. So I end up with SSH and SCP… quadlets and podman-systemd solves those problems I have reasonably well and OPs post is very valuable because it builds awareness of a solution that solves my problems.