Hacker News Reader

Comment by nomadiccoder | Hacker News Reader

It took me a long time to come to terms with this fact. I was once asked during an interview what I wouldnt run in k8s and I said legacy apps and hardware specific apps. Now I think that for many applications cloud run or cloud function can reduce the complexity of software delivery. It takes a team just to manage the k8s infra while an app team can be responsible for their own cloud run app.

View on HN

When I talk to people about k8s, if they haven't containerized their apps yet, I generally recommend starting with a simple CAAS setup and then, if you need some of the flexibility and power that k8s provides, then move those apps into a cluster.

It can do a lot of cool stuff, but there's plenty of complexity there, and there are quite a few potential nasty surprises in there (from a security standpoint anyway, which is where I focus)

By cloud function, do you mean something like AWS Lambda?

OP is using google cloud/GCP, cloud functions and cloud run are google cloud serverless offerings. Cloud functions is comparable to lambda, cloud run is basically a kubernetes-based PaaS.

CFs are higher level than Lambda, they can implement HTTP endpoints directly. More like Serverless framework, or a combination of API Gateway + Lambda. And they have good container support, Lambda container support is a bit iffy.

Thanks both for explaining. Now I understand why, recently AWS Lambda added support for invocation URLs. Or I thought they did but the page seems to have been taken down now.

Reply on news.ycombinator.com