undefined | Better HN

0 pointsXCSme1y ago0 comments

Why necessarily Kubernetes?

For many applications, it's enough to spin up a VPS/plain Docker container, and it will run fine for many, many years, without adding the Kubernetes complexity on top.

If the application is easy to install and autoconfigures itself, it's even better than having to configure everything yourself or create multi-server Kubernetes clusters.

0 comments

marcosdumay1y ago

Why you should use kubernetes? You most likely shouldn't.

But why should you learn kubernetes? Because everybody else is using it, whether they should or not. Very few people manage to work alone on IT.

But anyway, every single possible OT user needs something like kubernetes. It comes first at the scaling requirements.

pdimitar1y ago

Learning k8s carries a significant cognitive cost. I've learned hundreds of technologies in my 22+ years of career and I am not about to proactively learn something that people started making certification courses for (and some are quite long, we're talking weeks of training daily). And I am definitely not proactively learning it if it's only 1% likely I'll need it. (I am now working at the second company that actually truly benefits from k8s. Out of 15+.)

I have proactively learned what can k8s do and why is it useful however. That's a context that's very needed because k8s is also a huge investment and you should really know the pros and cons before jumping in. That I did.

j / k navigate · click thread line to collapse