[kryptn]

> 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.

[aduwah]

I think what happened is:"Chatgpt generate me a ragebait for HN about serverless and a k8s-engineer"

[js4ever]

here it is:

Title: Serverless is eating Kubernetes—and that's a good thing

After 6 years of watching K8s engineers over-engineer themselves into a corner with YAML spaghetti, I finally moved a production workload to AWS Lambda + EventBridge + DynamoDB. You know what happened?

Nothing broke. It just worked.

No Helm charts. No Ingress hell. No cluster upgrades at 3am because of CVEs in some sidecar no one uses anymore. The whole app is now ~300 lines of infra code and it scales from 0 to 10k RPS without me touching anything.

Meanwhile, the K8s crowd is still debating which operator to use to restart a pod that keeps crashing because someone misconfigured a liveness probe. Or building internal platforms to abstract away the abstraction they just built last quarter.

Remind me again what the value-add of Kubernetes is in 2025? Other than keeping a whole cottage industry of "DevOps" engineers employed?

Serverless isn’t the future. It’s the present. And K8s? It’s the next OpenStack—just slower to die because it has better branding.

[renatovico]

kkk, busted, trying a new shine thing :)

[teekert]

Can't we think if another name for "serverless"? Like OS-less? Stackless? By now it's pretty well known but it's confusing to anyone first hearing it. Like calling a city buildingless, oh but when you call for a building it's just there.

[sirtaj]

Perhaps CGI 2.0, or EvenFasterCGI.