Should "easy" and "kubernetes" ever really be in the same sentance?
Not being snarky, just realistic - I feel like cloud providers sell "kubernetes" as the only way to properly develop apps, because you can be cloud-agnostic, without lock-in, you have full control over your infrastructure.
Without realising, that for most projects, running a kubernetes stack requires a person just for tuning and maintainance. Kubernetes is great - when you hit massive problems of scalability, but most people aren't going to be facing the problems kubernetes solves.
These days it feels like the real value of kubernetes is not the ability to "planet scale" but actually the control-plane API. With tools like kind, it actually is really easy to get going locally, no cloud needed.
I see no reason to not use it, even if your deployment cluster lives on a single vm. The API is worth it.
delivering your service/app via kubernetes is slowly becoming the standard way, just like an universal binary format. so as a developer you should build towards delivery for kubernetes.
but you are certainly right that one should avoid running your own kubernetes infrastructure - at least until you can afford the accompanying expenses
Not being snarky, just realistic - I feel like cloud providers sell "kubernetes" as the only way to properly develop apps, because you can be cloud-agnostic, without lock-in, you have full control over your infrastructure.
Without realising, that for most projects, running a kubernetes stack requires a person just for tuning and maintainance. Kubernetes is great - when you hit massive problems of scalability, but most people aren't going to be facing the problems kubernetes solves.