google-cloud-run

问题 I am failing to get a basic Angular app deploying to Google Cloud Run. The error would suggest it is not being served correctly at port 8080, but running locally on my machine localhost:8080 displays the app. So possibly I need something extra for cloud run, if anybody has some idea? The details are as follows: I create a basic angular app ng new test-app The Dockerfile is as follows FROM node:latest as node WORKDIR /app COPY . . RUN npm install RUN npm run build --prod ENV PORT=8080 FROM

问题 I am trying to use Cloud run with private GKE cluster. I created the cluster using the below command: gcloud beta container clusters create cluster-name \ --create-subnetwork name=cloud-run-subnet \ --enable-master-authorized-networks \ --enable-ip-alias \ --enable-private-nodes \ --enable-private-endpoint \ --master-ipv4-cidr 172.16.0.32/28 \ --no-enable-basic-auth \ --no-issue-client-certificate \ --addons=HorizontalPodAutoscaling,HttpLoadBalancing,Istio,CloudRun \ --machine-type=n1

问题 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 ? 回答1: Neither Cloud Functions nor Cloud Run are able to support persistent socket connections for the same reasons. Each

问题 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

问题 Is there any advantage if I use Cloud Run instead of deploying a normal service/container in GKE? 回答1: 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,

问题 I have been diving into a Stackdriver Trace integration on Google Cloud Run. I can get it to work with the agent, but I am bothered by a few questions. Given that The Stackdriver agent aggregates traces in a small buffer and sends them periodically. CPU access is restricted when a Cloud Run service is not handling a request. There is no shutdown hook for Cloud Run services; you can't clear the buffer before shutdown: the container just gets a SIGKILL. This is a signal you can't catch from

问题 The current documentation (https://cloud.google.com/run/quotas#cloud_run_limits) states there is a 15 minute maximum timeout permitted (configurable) for a cloud run request. Is this the limit on GKE as well, or may it be possible to configure GKE and the deployment to permit, say, a 90 minute timeout? 回答1: The request timeout for Cloud Run on GKE services can go beyond 15 minutes. You can change this using the --timeout flag: gcloud beta run services update [SERVICE] --timeout=[TIMEOUT] Read

问题 I want to run a service on Google Cloud Run that uses Cloud Memorystore as cache. I created an Memorystore instance in the same region as Cloud Run and used the example code to connect: https://github.com/GoogleCloudPlatform/golang-samples/blob/master/memorystore/redis/main.go this didn't work. Next I created a Serverless VPC access Connectore which didn't help. I use Cloud Run without a GKE Cluster so I can't change any configuration. Is there a way to connect from Cloud Run to Memorystore?

问题 After reading the docs on both Cloud Run and Firebase Cloud Functions, I have a few questions I want to clear up: Does Cloud Run basically act as a container image storage/deploying mechanism? If I have 2 websites and have them as separate containerized images, does Cloud Run just deploy the specified one given the trigger? Integrating Cloud Run with Firebase Cloud Functions as the trigger, will there be an additional layer of latency? While latency times are never known, FCFs inherently have

问题 There is not documentation that I can find about the storage that Google Cloud Run has. For example, does it contains few Gigabyte storage as we create a VM? If not, is there a '/tmp' folder that I can put data temporarily into during the request? What's the limitation if available? If neither of them available, what's the recommendation if I want to save some temporary data while running Cloud Run? 回答1: Cloud Run is a stateless service platform, and does not have any built-in storage