> To a k8s engineer, serverless means “no servers”!
I'd assume a majority of people working with k8s knows what serverless is and where Functions as a Service work more generically.
The rest of the post just seems to be full of strawman arguments.
who is this kubernetes engineer villain? It sounds like a bad coworker at a company with a toxic culture, or a serverless advocate complaining at a bar after a bad meeting.
> k8s is great for container orchestration and complex workloads, while serverless shines for event-driven, auto-scaling applications.
> But will a k8s engineer ever admit that?
Of course. I manage k8s clusters in aws with eks. We use karpenter for autoscaling. A lot of our system is argo workflows, but we've also got a dozen or so services running.
We also have some large step functions written by a team that chose use lambda because aws can handle that kind of scaling much better than we would have wanted to in k8s.
I'd assume a majority of people working with k8s knows what serverless is and where Functions as a Service work more generically.
The rest of the post just seems to be full of strawman arguments.
who is this kubernetes engineer villain? It sounds like a bad coworker at a company with a toxic culture, or a serverless advocate complaining at a bar after a bad meeting.
> k8s is great for container orchestration and complex workloads, while serverless shines for event-driven, auto-scaling applications.
> But will a k8s engineer ever admit that?
Of course. I manage k8s clusters in aws with eks. We use karpenter for autoscaling. A lot of our system is argo workflows, but we've also got a dozen or so services running.
We also have some large step functions written by a team that chose use lambda because aws can handle that kind of scaling much better than we would have wanted to in k8s.