google-cloud-run

I've been researching the new options to run Docker containers in Google Cloud Run, however, there seems to be no advice on whether or not one should run MySQL on Cloud run, apparently, I know it isn't a web service, and I understand in the Official Google Documentation for GCP, Google would probably just tell people to kindly use Cloud SQL (their SQL Offering), I haven't found any advice online about "running mysql on cloud run", so I thought I'd ask here. Will startup times from cold starts decrease performance of the solution? (assuming one uses a Bucket for storing the stuff) Running a SQL

My understanding is that to establish a persistent socket connection using socket.io the Node.js server should be always running. With Google Cloud Functions there isn't an always running Node.js server, so keeping a socket connection alive is not possible. Is Cloud Run with a running Node.js server the best option to handle multiple socket connections using socket.io ? Neither Cloud Functions nor Cloud Run are able to support persistent socket connections for the same reasons. Each request has a timeout that can't be infinite. If you want to use socket.io effectively, you will need a

Is there any advantage if I use Cloud Run instead of deploying a normal service/container in GKE? I will try to add my perspective. This answer does not cover running containers in Google Cloud Run Kubernetes. The reason is that we wanted an almost zero cost solution for a legacy PHP website. Cloud Run fit perfectly and we had an easy time both porting the code and learning Cloud Run. We needed to do something with a legacy PHP website. This website was running on Windows Server 2012, IIS and PHP 7.0x. The cost was over $100.00 per month - mostly for Windows licensing fees for a VM in the

I'm using Cloud Run on Google Kubernetes Engine and I'm able to deploy and access services without a problem. But since I'm running on GKE and paying for the cluster 24/7 it makes no sense to scale a deployment to zero and always have a cold start for the first request. I've found that's it's possible to set minScale for the Knative autoscaler to disable scale to zero here , here and here , but I have no idea where to put it. There are a lot of configurations, services and workloads inside GKE for Isito and Knative-Serving, but I couldn't find anything matching. Which file or configuration do

I'm using managed CloudRun to deploy a container with concurrency=1 . Once deployed, I'm firing four long-running requests in parallel. Most of the time, all works fine -- But occasionally, I'm facing 500's from one of the nodes within a few seconds; logs only provide the error message provided in the subject. Using retry with exponential back-off did not improve the situation; the retries also end up with 500s. StackDriver logs also do not provide further information. Potentially relevant gcloud beta run deploy arguments: --memory 2Gi --concurrency 1 --timeout 8m --platform managed What does