[LeBit]

I don't understand the hate regarding K8s.

What's wrong with developing software knowing it will be hosted on a k8s cluster?

You can install a local k8s cluster will plenty of tools helping you with secrets management, observability, ingress, scaling, storage.

Why the hate?

[KRAKRISMOTT]

Because no engineer building application software wants to specify their infra down to the component level. Infra is awesome when it is Somebody Else's Problem. Docker compose was popular, Heroku was popular, Vercel is popular. Infra is good whenever there are reasonable defaults, good ergonomics, and requires no maintenance. Kubernetes is a DIY cloud solution. It's great if you are trying to build AWS/GCP/Azure, not so great if you want to deploy your app for the cheapest cost possible while not being constrained by the limitations of Vercel/Heroku.

The worst is clouds like fly.io that believe their value prop comes from stuff like "edge computing" while their main offering is half baked, under documented, and unreliable. People want better, cheaper managed infrastructure. Good managed infra should be small overhead on top of the raw compute cost. Nobody complains about LAMP PHP deployments because it was good value and offered what people wanted.

[noop_joe]

I'd love to connect with you and talk more about this! I'm working for a company building something that addresses the problems you describe [1], ditto for pricing model.

email is in my bio :-)

1. https://noop.dev

[skydhash]

It’s often an overkill solution. Most often you only need a VM and a few scripts to help with backup and deployments. Which can be done really cheap. But you bring in k8s, which is a nice abstraction, but often more complex than the services it hosts.

[yen223]

Kubernetes provides good abstractions for managing deployments, but Kubernetes also comes with massive overheads. The overheads come in terms of the many yaml files needed to define services, and in terms of complexity of the underlying infrastructure for hosting the cluster itself.

If you were in a bigcorp in charge of orchestrating 1000s of services, that overhead could be worth it.

However, if you were a solo dev trying to deploy one service, that overhead is really bad.