Hacker News new | ask | show | jobs
by inscrutable 2355 days ago
started using this... pretty awesome vs the wall of yaml it replaces. Not suitable for all workloads (max 1cpu/2 gigs ram, 4 minute max pod startup time, can't do background work when not serving a request). But it replaces cert-manager, ingress-nginx, oauth2-proxy, k8s service, k8s deployment, k8s secret, k8s configmap, k8s hpa, k8s pdb, helm charts and cluster management.
2 comments

Disclaimer: I work closely on Cloud Run as an SRE.

IF you want, you can still have it by use "Cloud Run for Anthos", and deploy your container to your GKE cluster with the same Knative API. This allows you to have more control on memory/CPU etc.

Thanks, although unfortunately I'm not in the price bracket for Anthos (starts at 120k/year or so I believe).
I believe there's no requirement if you just want to use Anthos on GKE (I could be wrong though, Anthos is relatively new).

Alternatively, if what you really want is the ease to manage and deploy containers and automatically scale according to traffic, my understanding is you can always use the open source Knative project with your Kubenetes cluster. This provide you the exact same API supported by Cloud Run and makes it very easy to migrate from managed Cloud Run to on-prem K8s cluster (or K8s clusters from other Cloud vendors).

thanks, I hope you're right, GCP doesn't appear to be clear on this point, seems to be offering free trial up to May 2020 and then who know. I'm aware of the ability to set it up from open source which is a great fallback!
Yes that's unnecessarily complicated due to the naming. I can't find anything on the Cloud Run add-on for GKE by searching "GKE Anthos".

This doc suggest you just need to enable Cloud Run add-on on your GKE cluster to use it: https://cloud.google.com/run/docs/gke/setup

I tried out Azure Container Instances a while back, and the startup times were also what killed it for me - they were all over the shop. It was 1-2 years ago, so I don't recall exactly and things may well have improved now, but I seem to recall they ranged from 1-5m.
So far what I've observed is <10s cold-start times on GCR. This is a fairly lightweight web app written using Undertow in Java so carries a JVM as overhead.