Question

Your team runs a public-facing REST API on Cloud Run. During an unexpected traffic surge, Cloud Run scaled out to hundreds of container instances, causing a large unexpected bill and exhausting your downstream Cloud SQL connection pool. You need to cap how many instances the service can create while keeping the deployment otherwise unchanged. What should you do?

Accepted Answer

Deploy a new revision with the --max-instances flag set to an appropriate ceiling on the Cloud Run service.

Answer

Set the --concurrency flag to 1 so that each instance handles only one request at a time.

Answer

Request a lower quota for the Cloud Run API in the project via a quota decrease request.

Answer

Add a Cloud Monitoring alerting policy on instance count and manually delete instances when it fires.