As someone who just went from zero to a working Kubernetes implementation, like a lot of things in tech, the problem isn't the tool: it's how others explain it.

The tool is excellent and extremely well-conceived. Being able to spin up a highly scalable fault-tolerant system with a few manifest files is impressive. The only frustration I ran into was trying to understand which files I needed when vs. what was unnecessary and intended for a special use case.

It depends on your scale of course. It’s not like “the industry” just wants to make things complicated for the fun of it. There comes a point where you’ll need more than one server to host your web app and when you do Kubernetes provides a nice abstraction in addition to providing a ton of other useful things at scale like infrastructure as code to zero downtime, continuous deployments.

> It’s not like “the industry” just wants to make things complicated for the fun of it.

Doesn't it? I think that there are plenty of folks who want to make things more complicated, because complicated things are fun, while just making things work can be a pain but also boring.

Thanks I got the gist. Peaking at our internal website yes we extensively use K8 guess it is needed there.