3 ms·

Attempting a serious answer, because I agree most things can be run on a Pi and be fine. Let's say you're a developer who's comfortable making Docker container

Attempting a serious answer, because I agree most things can be run on a Pi and be fine. Let's say you're a developer who's comfortable making Docker containers and running them locally. One day, you learn that you could go to Azure|Google|$OTHER and spin up something called Kubernetes, push your container, and now you get a trove of features like scaling, availability, health checks, the safety that you can lose a node and stay online. That sounds appealing to me. Of course, the marketing materials are never the same as where the rubber meets the road, but you stand up your service and all is well. It's an appealing offer. It's why people use Heroku. If all you have to do is one-click a cluster and go, why wouldn't you want to do that?

TheNewsIsHere 4y ago
> It's an appealing offer. It's why people use Heroku. If all you have to do is one-click a cluster and go, why wouldn't you want to do that? I think you’ve hit upon what seems evident in this discussion to me, but that doesn’t seem to be highlighted well. Even the most ardent Kubernetes advocates here are noting it’s not a panacea. It’s simply solving a need that exists at an immense scale. Underlying all of that, though, is a need to understand what you’re deploying no matter what it is. Click to deploy is very tempting, but should only be undertaken when you have an understanding of what you’re clicking and the how and why of the deployment process, the technology stack that makes it possible, etc.