[bvandewalle]

I'm using Kubernetes extensively in my day to day work and once you get it up and running and learn the different abstraction, it becomes a single API to manage your containers, storage and network ingress needs. Making it easy to take a container and getting it up and running in the cloud with an IP address and a DNS configured in a couple API calls (or defined as YAMLs).

That being said, I will also be the first one to recognize that PLENTY of workloads are not made to run on Kubernetes. Sometimes it is way more efficient to spawn an EC2/GCE instance and run a single docker container on it. It really depends on your use-case.

If I had to run a relatively simple app in prod I would never use Kubernetes to start with. Kubernetes starts to pay itself off once you have a critical mass of services on it.

[harpratap]

One could argue if you have a tiny set of services you are better off using a managed offering like AWS Lambda or Cloud Run

[garethmcc]

There are organisations with 1000's of services on Serverless seeing enormous benefits in reduced management overhead and reduced costs compared to the Kubernetes solution they previously ran.

[bvandewalle]

My issue with serverless though is that you need to refactor your code to make it work specifically for it. If you don't start to think serverless on day one it gets more and more difficult to convert to it down the road.