Question Details

No question body available.

Tags

google-cloud-platform google-cloud-run

Answers (2)

Accepted Answer Available
Accepted Answer
April 18, 2025 Score: 0 Rep: 2,950 Quality: Medium Completeness: 10%

I used to deploy in europe-west1 because of the need of custom domain mappings. As a test purpose I deployed it to europe-west8, it works, but it does not support custom domain mappings. Then I tried to deploy it on europe-west4, and it works as well, so the problem must be europe-west1.

April 18, 2025 Score: 0 Rep: 329 Quality: Low Completeness: 50%

There might be insufficient capacity for that region – customers may not receive sufficient compute resources for their workload. This can lead to elevated latency and errors.

Cloud Run is a multi-tenant system. All customer services and jobs in a Cloud Run region share a pool of compute resources. I would suggest trying after a couple of hours.

Speaking of tenants, another reason this happens is if tenant projects are missing on europe-west1 (for your project).

Try disable and re-enable the Cloud Run API to try and kickstart the tenant project creation for the region.

gcloud services disable run.googleapis.com --force

Then redeploy and see if there’s any improvement.