> Basically removes all of the major drawbacks to move to serverless

What about cold starts, debugging and runaway expenses?

Since the technology is based on knative, it should in theory be possible to run these on a local k8s instance. It would support some debugging use cases.

I do agree as far as cold starts and runaway expenses go, although those issues seem inherent with FaaS.

The biggest issue isn’t being able to run locally, it’s getting access to systems where an unexpected error is happening in production that didn’t happen in dev.

For expenses, it would be nice if there was a way to automatically shut off or throttle traffic after $X a month.

I agree, and looking through some of the doc it looks very easy to set up, but note AWS has Fargate, which is "a FaaS platform without vendor lock-in, supported by a major cloud vendor, and uses regular containers."

Potential to be huge for sure, but with the way Google sunsets projects on the regs, I'm not sure I fully trust it as a robust solution long term. Granted with container-based-deployments, it should be trivial to switch between services which would mitigate that. It's certainly interesting, but I may wait a year or so before I trust it for prod.